From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Greg KH <greg@kroah.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 0/2] Add dev_sysdata and use it for ACPI
Date: Mon, 13 Nov 2006 17:07:45 +1100 [thread overview]
Message-ID: <1163398066.4982.282.camel@localhost.localdomain> (raw)
In-Reply-To: <17751.65522.993927.170279@cargo.ozlabs.ibm.com>
On Mon, 2006-11-13 at 16:17 +1100, Paul Mackerras wrote:
> Greg KH writes:
>
> > Care to respin these patches with this change?
> >
> > And yes, I don't see a problem with such a change like this for 2.6.20,
> > it's pretty simple.
>
> I need to put Ben's "Add arch specific dev_archdata to struct device"
> patch into my tree in the for-2.6.20 branch, because it creates
> include/asm-powerpc/device.h, and I have other patches queued up which
> touch include/asm-powerpc/device.h.
>
> Greg, if you want you can drop that patch, and Linus' tree will get it
> via my tree, or if that's difficult, Linus' tree will get it from both
> directions. I'm sure git will sort it out. :)
Greg: Note that the patch paulus has is the respin I posted on Saturday
with the name change and the use of include/asm-generic/ as suggested by
Steven.
Ben.
prev parent reply other threads:[~2006-11-13 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 0:45 [PATCH 0/2] Add dev_sysdata and use it for ACPI Benjamin Herrenschmidt
2006-11-09 16:04 ` Cornelia Huck
2006-11-09 22:35 ` Benjamin Herrenschmidt
2006-11-10 5:48 ` Greg KH
2006-11-10 9:44 ` Benjamin Herrenschmidt
2006-11-13 5:17 ` Paul Mackerras
2006-11-13 6:07 ` Benjamin Herrenschmidt [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=1163398066.4982.282.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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