From: Ingo Molnar <mingo@elte.hu>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Andres Salomon <dilinger@queued.net>,
devicetree-discuss@lists.ozlabs.org, x86@kernel.org,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
Mitch Bradley <wmb@laptop.org>,
linux-kernel@vger.kernel.org,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Subject: Re: [PATCH 2/2] x86: of: define irq functions to allow drivers/of/* to build on x86
Date: Fri, 10 Sep 2010 20:14:58 +0200 [thread overview]
Message-ID: <20100910181458.GA7243@elte.hu> (raw)
In-Reply-To: <20100910172538.GC11284@angua.secretlab.ca>
* Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Sep 10, 2010 at 06:01:51AM -0700, Andres Salomon wrote:
> >
> > - Define a stub irq_create_of_mapping for x86 as a stop-gap solution until
> > drivers/of/irq is further along.
> > - Define irq_dispose_mapping for x86 to appease of_i2c.c
> >
> > Signed-off-by: Andres Salomon <dilinger@queued.net>
>
> Applied to my test-devicetree branch. I'll need an ack from the x86
> maintainers before I put it into my -next branch.
The purpose of the patch is not clear to me. What does it do and why?
The changelog says it's a stopgap measure - what exactly is the long
term plan and how long will it take?
Thanks,
Ingo
next prev parent reply other threads:[~2010-09-10 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 13:01 [PATCH 2/2] x86: of: define irq functions to allow drivers/of/* to build on x86 Andres Salomon
2010-09-10 17:25 ` Grant Likely
2010-09-10 18:14 ` Ingo Molnar [this message]
2010-09-10 18:21 ` Grant Likely
2010-09-21 2:06 ` Andres Salomon
2010-09-21 2:32 ` H. Peter Anvin
2010-09-21 9:45 ` Thomas Gleixner
2010-09-21 16:11 ` Andres Salomon
2010-09-21 16:27 ` Thomas Gleixner
2010-09-21 19:27 ` Grant Likely
2010-09-21 9:43 ` Thomas Gleixner
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=20100910181458.GA7243@elte.hu \
--to=mingo@elte.hu \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dilinger@queued.net \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stephen.neuendorffer@xilinx.com \
--cc=tglx@linutronix.de \
--cc=wmb@laptop.org \
--cc=x86@kernel.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