From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mingo <mingo@redhat.com>
Subject: Re: linux-next: Tree for April 10 (ftrace)
Date: Thu, 10 Apr 2008 15:07:48 -0700 [thread overview]
Message-ID: <20080410150748.1bf2a8a8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080410181404.b76939a6.sfr@canb.auug.org.au>
On Thu, 10 Apr 2008 18:14:04 +1000 Stephen Rothwell wrote:
> Hi all,
>
> [I have been asked to provide a summary of changes before the biolerplate
> so here goes (please tell me if this is what you want or not). I am not
> going to try to describe the changes in the individual trees, just the
> interactions between them.]
>
> Changes since next-20080410:
>
> I no longer revert "x86: phase out forced inlining".
> There is a new conflict in arch/s390/lib/uaccess_pt.c between the s390 and
> kvm trees.
> There is a new trivial white space conflict in arch/ia64/kernel/mca.c.
> I no longer need to revert "wusb: add the wireless usb stack to Linux".
>
> Today's Next/Trees file is lying: the x86-latest and sched-latest trees
> did not merge/build correctly so have not been included.
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> (tar balls at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
trace selftest build fails when CONFIG_RT_MUTEXES=n:
next-20080410/kernel/trace/trace_selftest.c:413: error: implicit declaration of function 'rt_mutex_setprio'
make[3]: *** [kernel/trace/trace.o] Error 1
Possible fixes:
kernel/trace/Kconfig: SCHED_TRACER can depend on RT_MUTEXES
or there can be a stub for rt_mutex_setprio() when RT_MUTEXES=n
And kernel/trace/trace_selftest.c still needs #include <sched.h> added to it.
---
~Randy
next prev parent reply other threads:[~2008-04-10 22:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 8:14 linux-next: Tree for April 10 Stephen Rothwell
2008-04-10 10:24 ` [BUG] linux-next: Tree for April 10 - kernel panic while loading ata driver on powermac Kamalesh Babulal
2008-04-10 10:45 ` Jeff Garzik
2008-04-10 11:02 ` Kamalesh Babulal
2008-04-10 11:32 ` Alan Cox
2008-04-10 12:14 ` Jeff Garzik
2008-04-10 12:03 ` Bartlomiej Zolnierkiewicz
2008-04-10 17:14 ` Bartlomiej Zolnierkiewicz
2008-04-10 18:25 ` Kamalesh Babulal
2008-04-10 19:16 ` Bartlomiej Zolnierkiewicz
2008-04-10 17:42 ` linux-next: Tree for April 10 Greg KH
2008-04-10 18:07 ` [BUG] linux-next: April 10 - kernel oops at kmem_cache_alloc () regression from April 9 kernel Kamalesh Babulal
2008-04-11 17:56 ` Suresh Siddha
2008-04-14 13:14 ` Kamalesh Babulal
2008-04-10 19:34 ` linux-next: Tree for April 10: generic pci_enable_resources() strikes again Mariusz Kozlowski
2008-04-14 1:48 ` Stephen Rothwell
2008-04-14 4:28 ` Greg KH
2008-04-14 4:49 ` Stephen Rothwell
2008-04-10 22:07 ` Randy Dunlap [this message]
2008-04-10 22:09 ` linux-next: Tree for April 10 (arch/x86) Randy Dunlap
2008-04-11 7:46 ` Ingo Molnar
2008-04-11 15:19 ` Randy Dunlap
2008-04-11 15:26 ` Al Viro
2008-04-14 8:12 ` Ingo Molnar
2008-04-14 8:22 ` Al Viro
2008-04-14 8:34 ` Ingo Molnar
2008-04-14 8:43 ` Jakub Jelinek
2008-04-14 9:30 ` Al Viro
2008-04-14 9:37 ` David Miller
2008-04-14 8:40 ` Jakub Jelinek
2008-04-14 22:28 ` Randy Dunlap
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=20080410150748.1bf2a8a8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome