linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Geert Uytterhoeven' <geert@linux-m68k.org>,
	'Arnd Bergmann' <arnd@arndb.de>
Cc: 'Lucas Stach' <l.stach@pengutronix.de>,
	devicetree@vger.kernel.org,
	'Grant Likely' <grant.likely@linaro.org>,
	'Rob Herring' <robh+dt@kernel.org>,
	'Bjorn Helgaas' <bhelgaas@google.com>,
	'Magnus Damm' <damm@opensource.se>,
	'Ben Dooks' <ben.dooks@codethink.co.uk>,
	'linux-pci' <linux-pci@vger.kernel.org>,
	'Linux-sh list' <linux-sh@vger.kernel.org>,
	'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [PATCH v2] of/irq: provide int of_irq_parse_and_map_pci wrapper
Date: Wed, 28 May 2014 10:35:43 +0900	[thread overview]
Message-ID: <002301cf7a15$23eb5180$6bc1f480$%han@samsung.com> (raw)
In-Reply-To: <CAMuHMdXXFmxmq9H1fuc7fRg8BHQ+3m6=4mPDe5FjL0hLLvwUUw@mail.gmail.com>

On Friday, May 09, 2014 6:10 PM, Geert Uytterhoeven wrote:
> On Fri, May 9, 2014 at 11:03 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > The pci-rcar driver is enabled for compile tests, and this has
> > now shown that the driver cannot build without CONFIG_OF,
> > following the inclusion of f8f2fe7355fb "PCI: rcar: Use new OF
> > interrupt mapping when possible":
> >
> > drivers/built-in.o: In function `rcar_pci_map_irq':
> > :(.text+0x1cc7c): undefined reference to `of_irq_parse_and_map_pci'
> >
> > As pointed out by Ben Dooks and Geert Uytterhoeven, this is actually
> > supposed to build fine, which we can achieve if we make the
> > declaration of of_irq_parse_and_map_pci conditional on CONFIG_OF
> > and provide an empty inline function otherwise, as we do for
> > a lot of other of interfaces.
> >
> > This lets us build the rcar_pci driver again without CONFIG_OF
> > for build testing. All platforms using this driver select OF,
> > so this doesn't change anything for the users.
> 
> Thanks!
> 
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > Cc: Magnus Damm <damm@opensource.se>
> > Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> > Cc: Ben Dooks <ben.dooks@codethink.co.uk>
> > Cc: linux-pci@vger.kernel.org
> > Cc: linux-sh@vger.kernel.org
> 
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Reviewed-by: Jingoo Han <jg1.han@samsung.com>

Best regards,
Jingoo Han


      reply	other threads:[~2014-05-28  1:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  6:58 [PATCH] of/irq: provide int of_irq_parse_and_map_pci wrapper Arnd Bergmann
2014-05-09  7:11 ` Geert Uytterhoeven
2014-05-09  8:28 ` Lucas Stach
2014-05-09  8:45   ` Arnd Bergmann
2014-05-09  8:54     ` Lucas Stach
2014-05-09  8:56     ` Geert Uytterhoeven
2014-05-09  9:03   ` [PATCH v2] " Arnd Bergmann
2014-05-09  9:09     ` Geert Uytterhoeven
2014-05-28  1:35       ` Jingoo Han [this message]

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='002301cf7a15$23eb5180$6bc1f480$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=arnd@arndb.de \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bhelgaas@google.com \
    --cc=damm@opensource.se \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=grant.likely@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).