Devicetree
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	devicetree-discuss@lists.ozlabs.org,
	David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
	microblaze-uclinux@itee.uq.edu.au,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: Using devices trees on X86
Date: Tue, 29 Jun 2010 16:02:51 +1000	[thread overview]
Message-ID: <20100629160251.9e9fe7b1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTikEJluwUSTmG64jgQYAt_8YI7-gVA2iqOPKrM9W@mail.gmail.com>

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

Hi Grant,

On Mon, 28 Jun 2010 22:56:14 -0700 Grant Likely <grant.likely@secretlab.ca> wrote:
>
> I've got an Ack from David now.  I'll wait for more acks, and then
> pull the whole series of 5 into my devicetree-next branch.  It's
> certainly less invasive that some of the other changes arch changes
> I've taken through my tree.

Yes, certainly.  However, I have a plan to write a series of patches for
PowerPC that may clash some what, so if that is the case, I might ask Ben
to take the one patch as well.  Especially if the conflict turns up in
linux-next :-)

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

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

  reply	other threads:[~2010-06-29  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 17:57 Using devices trees on X86 Stephen Neuendorffer
     [not found] ` <0bcc23b9-2cbd-4465-b17c-7b3c2dff9fd3-+Ck8Kgl/v09CYczPSvLbDrjjLBE8jN/0@public.gmane.org>
2010-06-28 18:08   ` Grant Likely
2010-06-29  2:38 ` Stephen Rothwell
2010-06-29  2:42   ` [PATCH 1/5] microblaze: turn CONFIG_OF into a select Stephen Rothwell
     [not found]     ` <20100629124200.20ca24b7.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-06-29  9:57       ` Michal Simek
2010-06-29  2:43   ` [PATCH 2/5] powerpc: " Stephen Rothwell
2010-06-29  2:44   ` [PATCH 3/5] sparc: " Stephen Rothwell
     [not found]     ` <20100629124450.5e85bafe.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-06-29  3:11       ` David Miller
2010-06-29  2:45   ` [PATCH 4/5] of: define CONFIG_OF globally so architectures can select it Stephen Rothwell
2010-06-29  2:47   ` [PATCH 5/5] of: remove architecture CONFIG_OF definitions Stephen Rothwell
2010-06-29  9:58     ` Michal Simek
2010-06-29  5:56   ` Using devices trees on X86 Grant Likely
2010-06-29  6:02     ` Stephen Rothwell [this message]
     [not found]   ` <20100629123843.5f94d477.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-06-29 15:56     ` Stephen Neuendorffer

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=20100629160251.9e9fe7b1.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@monstr.eu \
    --cc=paulus@samba.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=stephen.neuendorffer@xilinx.com \
    /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