linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 1/3] of/irq: Export of_irq_get()
Date: Thu, 30 Oct 2014 16:17:19 +0200	[thread overview]
Message-ID: <2139081.L8ZrMAojpq@avalon> (raw)
In-Reply-To: <20141030141644.GE23852@katana>

On Thursday 30 October 2014 15:16:44 Wolfram Sang wrote:
> On Thu, Oct 30, 2014 at 03:59:36PM +0200, Laurent Pinchart wrote:
> > The function will be used by the I2C core which can be compiled as a
> > module.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> 
> I think it makes sense if I take this via I2C to get the dependencies
> for the later patches right?

It would be easier, yes.

> > ---
> > 
> >  drivers/of/irq.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/of/irq.c b/drivers/of/irq.c
> > index 1471e0a223a5..0d7765807f49 100644
> > --- a/drivers/of/irq.c
> > +++ b/drivers/of/irq.c
> > @@ -405,6 +405,7 @@ int of_irq_get(struct device_node *dev, int index)
> > 
> >  	return irq_create_of_mapping(&oirq);
> >  
> >  }
> > 
> > +EXPORT_SYMBOL_GPL(of_irq_get);
> > 
> >  /**
> >  
> >   * of_irq_get_byname - Decode a node's IRQ and return it as a Linux irq
> >   number

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2014-10-30 14:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 13:59 [PATCH 0/3] Delay I2C OF IRQ mapping until probe time Laurent Pinchart
     [not found] ` <1414677578-27412-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-10-30 13:59   ` [PATCH 1/3] of/irq: Export of_irq_get() Laurent Pinchart
2014-10-30 14:16     ` Wolfram Sang
2014-10-30 14:17       ` Laurent Pinchart [this message]
2014-10-31 18:20         ` Wolfram Sang
2014-10-31 20:58           ` Rob Herring
2014-11-04 15:55       ` Grant Likely
     [not found]     ` <1414677578-27412-2-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-11-07 18:05       ` Wolfram Sang
2014-10-30 14:27   ` [PATCH 0/3] Delay I2C OF IRQ mapping until probe time Thierry Reding
2014-10-30 13:59 ` [PATCH 2/3] i2c: core: Dispose OF IRQ mapping at client removal time Laurent Pinchart
     [not found]   ` <1414677578-27412-3-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-10-30 14:25     ` Thierry Reding
2014-11-07 18:03     ` Wolfram Sang
2014-10-30 13:59 ` [PATCH 3/3] i2c: core: Map OF IRQ at probe time Laurent Pinchart
     [not found]   ` <1414677578-27412-4-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-11-07 18:05     ` Wolfram Sang
2014-11-17 11:24   ` Geert Uytterhoeven

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=2139081.L8ZrMAojpq@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).