public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ["PATCH"] Linus breaks virtualbox-modules
Date: Thu, 21 Feb 2013 09:30:46 +0100	[thread overview]
Message-ID: <1361435446.14955.0@numa-i> (raw)
In-Reply-To: <kg2jnu$k8e$1@ger.gmane.org>

On 02/20/2013 02:40:16 PM, walt wrote:
> Now that kernel 3.8.0 is officially released, 'tis the season for  
> Linus to
> start breaking all of the third-party kernel modules he can, and  
> virtualbox-
> modules is the first (nvidia.ko and other kernel modules to follow,  
> probably ;)
> 
> Virtualbox-modules fails to build against today's kernel.git update  
> from Linus,
> with an error message that "MAX_PRIO is undefined" in  
> thread2-r0drv-linux.c.
> 
> The fix is happily very simple because he moved the definition of  
> MAX_PRIO
> into <linux/init_task.h>, so all you need to do is to add that  
> include near
> the top of thread2-r0drv-linux.c.
> 

Strange, but that doesn't happen for me.
I have vanilla 3.8.0 here and virtualbox-modules-4.2.6 builds just fine.
Am I special?

Helmut.



      parent reply	other threads:[~2013-02-21  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 13:40 [gentoo-user] ["PATCH"] Linus breaks virtualbox-modules walt
2013-02-20 14:04 ` Michael Hampicke
2013-02-20 20:23 ` Markos Chandras
2013-02-20 20:57 ` Mike Gilbert
2013-02-21  1:15   ` [gentoo-user] " walt
2013-02-21  1:53     ` Mike Gilbert
2013-02-21  2:33       ` Pandu Poluan
2013-02-21 10:00   ` [gentoo-user] " Joerg Schilling
2013-02-21 20:15     ` Bruce Hill
2013-02-22  5:30     ` Alon Bar-Lev
2013-02-22 10:27       ` Joerg Schilling
2013-02-22 21:44         ` Bruce Hill
2013-02-22 21:45         ` Bruce Hill
2013-02-21  8:30 ` Helmut Jarausch [this message]

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

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

  git send-email \
    --in-reply-to=1361435446.14955.0@numa-i \
    --to=jarausch@igpm.rwth-aachen.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox