From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Theodore Tso <tytso@MIT•EDU>, LKML <linux-kernel@vger•kernel.org>,
linuxppc-dev@ozlabs•org, linux-next@vger•kernel.org,
Paul Mackerras <paulus@samba•org>,
Dan Williams <dan.j.williams@intel•com>
Subject: Re: linux-next: Tree for March 20
Date: Wed, 19 Mar 2008 21:57:19 -0700 [thread overview]
Message-ID: <20080320045719.GA26938@kroah.com> (raw)
In-Reply-To: <20080320143953.8d6b5a60.sfr@canb.auug.org.au>
On Thu, Mar 20, 2008 at 02:39:53PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> 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/).
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log files
> in the Next directory. Between each merge, the tree was built with
> a ppc64_defconfig for powerpc and an allmodconfig for x86_64.
>
> I have started this tree by reverting the following:
> driver-core/driver-core-remove-no-longer-used-struct-class_device.patch
> should be merged late
> driver-core/ib-convert-struct-class_device-to-struct-device.patch
> conflicts with the infiniband tree
> driver-core/pm-make-wakeup-flags-available-whenever-config_pm-is-set.patch
> breaks non CONFIG_PM builds of drivers/serial/serial_core.c
These should be fixed tomorrow, I have new ones in my inbox to solve
these issues (I hope...)
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-20 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 3:39 linux-next: Tree for March 20 Stephen Rothwell
2008-03-20 4:21 ` Randy Dunlap
2008-03-20 15:14 ` Mauro Carvalho Chehab
2008-03-20 4:57 ` Greg KH [this message]
2008-03-20 6:17 ` Stephen Rothwell
2008-03-25 6:48 ` Stephen Rothwell
2008-03-25 7:31 ` Greg KH
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=20080320045719.GA26938@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tytso@MIT$(echo .)EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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