From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Bill Pemberton <wfp5p@virginia.edu>, Greg KH <greg@kroah.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: linux-next: manual merge of the gpio tree with the driver-core tree
Date: Fri, 30 Nov 2012 00:01:18 +0000 [thread overview]
Message-ID: <20121130000118.A68313E05AD@localhost> (raw)
In-Reply-To: <20121129155723.60035c6419fd9a00f46e4d69@canb.auug.org.au>
On Thu, 29 Nov 2012 15:57:23 +1100, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Grant,
>
> Today's linux-next merge of the gpio tree got a conflict in
> drivers/gpio/gpio-em.c between commit 3836309d9346 ("gpio: remove use of
> __devinit") from the driver-core tree and commit 7385500a49b7 ("gpio/em:
> convert to linear IRQ domain") from the gpio tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
Thanks Stephen.
Yes, please carry the fix.
g.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc drivers/gpio/gpio-em.c
> index 320a718,b007063..0000000
> --- a/drivers/gpio/gpio-em.c
> +++ b/drivers/gpio/gpio-em.c
> @@@ -234,41 -233,7 +233,7 @@@ static struct irq_domain_ops em_gio_irq
> .map = em_gio_irq_domain_map,
> };
>
> - static int __devinit em_gio_irq_domain_init(struct em_gio_priv *p)
> - {
> - struct platform_device *pdev = p->pdev;
> - struct gpio_em_config *pdata = pdev->dev.platform_data;
> -
> - p->irq_base = irq_alloc_descs(pdata->irq_base, 0,
> - pdata->number_of_pins, numa_node_id());
> - if (p->irq_base < 0) {
> - dev_err(&pdev->dev, "cannot get irq_desc\n");
> - return p->irq_base;
> - }
> - pr_debug("gio: hw base = %d, nr = %d, sw base = %d\n",
> - pdata->gpio_base, pdata->number_of_pins, p->irq_base);
> -
> - p->irq_domain = irq_domain_add_legacy(pdev->dev.of_node,
> - pdata->number_of_pins,
> - p->irq_base, 0,
> - &em_gio_irq_domain_ops, p);
> - if (!p->irq_domain) {
> - irq_free_descs(p->irq_base, pdata->number_of_pins);
> - return -ENXIO;
> - }
> -
> - return 0;
> - }
> -
> - static void em_gio_irq_domain_cleanup(struct em_gio_priv *p)
> - {
> - struct gpio_em_config *pdata = p->pdev->dev.platform_data;
> -
> - irq_free_descs(p->irq_base, pdata->number_of_pins);
> - /* FIXME: irq domain wants to be freed! */
> - }
> -
> -static int __devinit em_gio_probe(struct platform_device *pdev)
> +static int em_gio_probe(struct platform_device *pdev)
> {
> struct gpio_em_config *pdata = pdev->dev.platform_data;
> struct em_gio_priv *p;
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
next prev parent reply other threads:[~2012-11-30 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 4:57 linux-next: manual merge of the gpio tree with the driver-core tree Stephen Rothwell
2012-11-29 5:17 ` Greg KH
2012-11-30 0:01 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-07 4:05 Stephen Rothwell
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=20121130000118.A68313E05AD@localhost \
--to=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wfp5p@virginia.edu \
/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).