From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Greg KH <greg@kroah.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-next@vger.kernel.org
Subject: Re: linux-next: driver-core/pci merge failure
Date: Wed, 21 May 2008 10:25:35 +1000 [thread overview]
Message-ID: <20080521102535.a2c6cd1c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <200805201653.04543.jbarnes@virtuousgeek.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Hi all,
On Tue, 20 May 2008 16:53:04 -0700 Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> On Tuesday, May 20, 2008 4:31 pm Greg KH wrote:
>
> > Rafael, I'll be dropping the following patches from my tree:
> > driver-core/pm-introduce-new-top-level-suspend-and-hibernation-callbacks.p
> >atch
> > driver-core/pm-new-suspend-and-hibernation-callbacks-for-platform-bus-type.
> >patch
> > driver-core/pm-new-suspend-and-hibernation-callbacks-for-pci-bus-type.patch
> >
> > I'm guessing you want Jesse to also pick up the platform-bus one as
> > well, so that does not get lost.
> >
> > Is that ok?
>
> Sounds good, thanks Greg.
OK, so since Jesse put those three patches into the pci tree, I will
revert them from driver-core before I merge it into linux-next today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-05-21 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 2:03 linux-next: driver-core/pci merge failure Stephen Rothwell
2008-05-19 14:25 ` Rafael J. Wysocki
2008-05-19 15:22 ` Greg KH
2008-05-19 22:39 ` Rafael J. Wysocki
2008-05-20 5:31 ` Stephen Rothwell
2008-05-20 21:08 ` Jesse Barnes
2008-05-20 23:31 ` Greg KH
2008-05-20 23:40 ` Rafael J. Wysocki
2008-05-20 23:53 ` Jesse Barnes
2008-05-21 0:25 ` Stephen Rothwell [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=20080521102535.a2c6cd1c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).