From: Andres Salomon <dilinger@queued.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@lists.ozlabs.org,
David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/7] sparc: make drivers/of/pdt.c no longer sparc-only
Date: Sun, 10 Oct 2010 23:50:15 -0700 [thread overview]
Message-ID: <20101010235015.2954811f@uxo> (raw)
In-Reply-To: <20101011040443.GA23588@angua.secretlab.ca>
On Sun, 10 Oct 2010 22:04:43 -0600
Grant Likely <grant.likely@secretlab.ca> wrote:
> On Sun, Oct 10, 2010 at 02:09:05AM -0700, Andres Salomon wrote:
> > Whoops, that should've been 1/5, not 1/7. Two additional x86
> > patches snuck in there that are already in Grant's test-devicetree
> > branch.
>
> Note that of the two patches I'm carrying in test-devicetree, only one
> of them is actually able to move into linux-next at this present time.
>
> 1) of/irq: remove references to NO_IRQ in drivers/of/platform.c
>
> I'm putting this one into next-devicetree now
>
> 2) x86/of: define irq functions to allow drivers/of/* to build on x86
>
> I've not yet received an ack from the x86 maintainers on this, so I
> cannot put it into my next branch. (Sorry I didn't notice this
> earlier; it just dawned on me as I was looking over which patches I
> needed to move over). The same goes for the patch that actaully adds
> OF support for x86 OLPC. I'll need an ack from x86 folks before I
> merge it.
>
> g.
Okay. For reference, that patch is:
https://patchwork.kernel.org/patch/168662/
x86 folks, mind reviewing and providing an Ack or Nack?
next prev parent reply other threads:[~2010-10-11 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 8:43 Andres Salomon
2010-10-10 9:09 ` Andres Salomon
2010-10-11 4:04 ` Grant Likely
2010-10-11 6:50 ` Andres Salomon [this message]
2010-10-11 4:10 ` Grant Likely
2010-10-11 4:11 ` David Miller
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=20101010235015.2954811f@uxo \
--to=dilinger@queued.net \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome