linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Wu, Fengguang" <fengguang.wu@intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	Linus <torvalds@linux-foundation.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: origin tree build warning
Date: Tue, 19 Jan 2010 13:05:14 -0800	[thread overview]
Message-ID: <20100119210514.GD10928@kroah.com> (raw)
In-Reply-To: <20100119111226.c9405ac7.sfr@canb.auug.org.au>

On Tue, Jan 19, 2010 at 11:12:26AM +1100, Stephen Rothwell wrote:
> Hi Fengguang,
> 
> On Mon, 18 Jan 2010 16:40:39 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 18 Jan 2010 12:29:52 +0800 "Wu, Fengguang" <fengguang.wu@intel.com> wrote:
> > >
> > > On Mon, 18 Jan 2010 15:05:01 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > > >
> > > > > It actually looks like commit c29af9636 ("sysdev: Pass attribute in
> > > > > sysdev_class attributes show/store") referred to in the changelog for the
> > > > > above commit has not yet been applied to Linus' tree?
> > > >
> > > > Commit c29af9636 ("sysdev: Pass attribute in sysdev_class attributes
> > > > show/store") does appear in linux-next since next-20100111 (in the
> > > > driver-core quilt series - therefore intended for 2.6.34) (it will have a
> > > > different SHA1 today)
> > > 
> > > So let's queue 8ff410daa009c (sysdev: fix prototype for memory_sysdev_class show/store functions)
> > > in driver-core and delay it to 2.6.34?
> > 
> > Then it would need to be reverted from Linus' tree.
> 
> I have reverted commit 8ff410daa009c for today.  It looks like Greg
> already has the alternate patches queued in the driver-core tree to take
> care of this problem when it arises.
> 
> So, Greg, can you ask Linus to revert 8ff410daa009c (sysdev: fix
> prototype for memory_sysdev_class show/store functions), please?  Or
> should I?  Or should we hope he notices these emails? :-)

No, I think the patch in Linus's tree is correct, so I have fixed up my
tree now.

thanks,

greg k-h

  reply	other threads:[~2010-01-19 21:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  4:05 linux-next: origin tree build warning Stephen Rothwell
2010-01-18  4:14 ` Stephen Rothwell
2010-01-18  4:29   ` Wu, Fengguang
2010-01-18  5:40     ` Stephen Rothwell
2010-01-19  0:12       ` Stephen Rothwell
2010-01-19 21:05         ` Greg KH [this message]
2010-01-19 21:11           ` Greg KH
2010-01-19 23:47             ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  0:09 Stephen Rothwell
     [not found] <20100101112914.41bc5f77.sfr@canb.auug.org.au>
2010-01-01  0:34 ` Linus Torvalds
2010-01-01  1:02   ` Stephen Rothwell
2010-01-01  1:16     ` Rafael J. Wysocki
2009-12-17  0:10 Stephen Rothwell
2009-12-16  3:52 Stephen Rothwell
2009-12-13 23:24 Stephen Rothwell
2009-12-14  7:24 ` Joe Perches
2009-11-29 23:01 Stephen Rothwell
2009-10-30  3:30 Stephen Rothwell
2009-10-11 23:56 Stephen Rothwell
2009-08-25  0:11 Stephen Rothwell
2009-08-25  2:37 ` David Miller
2009-06-23  0:36 Stephen Rothwell
2009-06-22  1:01 [ofa-general] " Stephen Rothwell
2009-06-22  3:11 ` FUJITA Tomonori
2009-06-19  1:13 Stephen Rothwell
2009-06-19  8:45 ` Kristoffer Ericson
2009-06-19  0:27 Stephen Rothwell
2009-06-19  0:28 ` Stephen Rothwell
2009-06-11  1:27 Stephen Rothwell
2009-04-29  4:49 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=20100119210514.GD10928@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).