unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Brendan Tildesley <mail@brendan.scot>, 40190@debbugs.gnu.org
Subject: [bug#40190] v4l2loopback module builds with 5.4 but not 5.6
Date: Mon, 06 Apr 2020 13:01:59 +0200	[thread overview]
Message-ID: <877dys3mjc.fsf@nckx> (raw)
In-Reply-To: <e1125357-568a-18a7-7277-a489714b4deb@brendan.scot>

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

Brendan,

Brendan Tildesley 写道:
> I just made a package definition for v4l2loopback. It built 
> perfectly
> fine with Linux 5.4, but when i switched to 5.6.2 with the patch 
> that
> sets it to default, suddenly I get this error below. I was 
> wondering
> if anyone can tell if this is likely my fault, a guix bug with 
> 5.6, or
> an upstream bug I should report there? Thanks.

This is normal for kernel modules, which are expected to keep up 
with upstream kernel development.  It's already fixed upstream:

https://github.com/umlaeute/v4l2loopback/commit/54ef8e99720cbb447ad8e0d598ee05580b485391

It might apply cleanly to 0.12.3.

Kind regards,

T G-R

PS: Don't rely on mutable GitHub /archive/ tarballs, use GIT-FETCH 
instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2020-04-06 11:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k13gqhrw.fsf@ponder>
     [not found] ` <87sgi0le3g.fsf@ponder>
2020-03-23  4:08   ` [bug#40190] Linux-Libre 5.5.x Vagrant Cascadian
2020-03-30 17:32     ` Vagrant Cascadian
2020-03-30 17:34       ` Vagrant Cascadian
2020-03-31  0:10         ` [bug#40190] Linux-Libre 5.6 Vagrant Cascadian
2020-03-31 14:30           ` Marius Bakke
2020-03-31 17:44             ` Vagrant Cascadian
2020-03-31 18:35               ` Guillaume Le Vaillant
2020-04-03 23:28               ` Vagrant Cascadian
2020-04-03 23:29                 ` Vagrant Cascadian
2020-04-16 19:37                   ` Vagrant Cascadian
2020-04-17 19:26                     ` Mark H Weaver
2020-06-08 20:46                       ` [bug#40190] Linux-Libre 5.7 Vagrant Cascadian
2020-06-09  2:43                       ` [bug#40190] Linux-Libre 5.6 Leo Famulari
2020-04-06  4:12     ` [bug#40190] Works for me Brendan Tildesley
2020-04-06 10:38       ` [bug#40190] v4l2loopback module builds with 5.4 but not 5.6 Brendan Tildesley
2020-04-06 10:46         ` Danny Milosavljevic
2020-04-06 11:01         ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-08-05 21:29     ` bug#40190: Linux-Libre 5.5.x Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dys3mjc.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=40190@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).