mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@ozlabs.org, Theodore Tso <tytso@MIT.EDU>
Subject: Re: linux-next: Tree for March 20
Date: Thu, 20 Mar 2008 17:17:02 +1100	[thread overview]
Message-ID: <20080320171702.d7fca89b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080320045719.GA26938@kroah.com>

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

On Wed, 19 Mar 2008 21:57:19 -0700 Greg KH <greg@kroah.com> wrote:
>
> On Thu, Mar 20, 2008 at 02:39:53PM +1100, Stephen Rothwell wrote:
> > 
> > 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...)

Great, I look forward to it.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-20  6:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  3:39 Stephen Rothwell
2008-03-20  4:21 ` Randy Dunlap
2008-03-20 15:14   ` Mauro Carvalho Chehab
2008-03-20  4:57 ` Greg KH
2008-03-20  6:17   ` Stephen Rothwell [this message]
2008-03-25  6:48   ` Stephen Rothwell
2008-03-25  7:31     ` Greg KH
2008-03-20 10:47 ` [BUG] linux-next: Tree for March 20 kernel oops, when loading mpt fusion driver Kamalesh Babulal
2009-03-20  5:28 linux-next: Tree for March 20 Stephen Rothwell

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=20080320171702.d7fca89b.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dan.j.williams@intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tytso@MIT.EDU \
    /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

all inboxes | Powered by JetHome®