From: Wolfram Sang <wsa@the-dreams.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Jeremy Linton <lintonrjeremy@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Vignesh R <vigneshr@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/irq: export of_get_irq_byname()
Date: Wed, 26 Aug 2015 09:40:17 +0200 [thread overview]
Message-ID: <20150826074017.GA9479@katana> (raw)
In-Reply-To: <20150826102425.2dab3a6f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Wed, Aug 26, 2015 at 10:24:25AM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
>
> On Tue, 25 Aug 2015 17:04:02 -0700 Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >
> > Similarly to of_get_irq(), let's export of_irq_get_byname(), so if a bus core
> > can be compiled as a module (such as I2C) it can have access to the symbol.
> >
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Reported-by: kbuild test robot <fengguang.wu@intel.com>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> I applied that to linux-next today. Pelase get it applied to the i2c
> tree (with appropriate acks).
Waiting for Rob's Ack, then I'll pick it up...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-26 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 0:04 [PATCH] of/irq: export of_get_irq_byname() Dmitry Torokhov
2015-08-26 0:04 ` Dmitry Torokhov
2015-08-26 0:24 ` Stephen Rothwell
2015-08-26 0:24 ` Stephen Rothwell
2015-08-26 7:40 ` Wolfram Sang [this message]
2015-08-26 13:16 ` Rob Herring
2015-08-26 13:16 ` Rob Herring
2015-08-26 16:36 ` Wolfram Sang
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=20150826074017.GA9479@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=grant.likely@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lintonrjeremy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.