From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Samuel Ortiz <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] MFD: ab8500: pass AB8500 IRQ to debugfs code by resource
Date: Fri, 12 Apr 2013 12:48:53 +0200 [thread overview]
Message-ID: <201304121248.54005.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdatbhais8gP3rTRkz0Y1v816Uz8KL6ZhDsh+ByfbjXuxg@mail.gmail.com>
On Friday 12 April 2013, Linus Walleij wrote:
> On Fri, Apr 12, 2013 at 10:08 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 12 April 2013, Linus Walleij wrote:
>
> >> Actually, well, this one IRQ (the one I start to pass) is already
> >> domain-mapped to the global IRQ numberspace, so that one will
> >> be correct.
> >
> > I don't know if we're talking about the same thing here.
> >
> > My point was that passing a domain-mapped IRQ number into mfd_add_devices
> > with another domain will result in the attempt to map that number into
> > another domain, which does not work.
>
> Ah, yes you're right ... now I need to find some other way
> to pass this resource ... hm.
>
What is it actually needed for? In the code I'm looking at in linux-next
it only gets passed to a function that ignores it.
Arnd
next prev parent reply other threads:[~2013-04-12 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 8:42 [PATCH] MFD: ab8500: pass AB8500 IRQ to debugfs code by resource Linus Walleij
2013-04-11 14:33 ` Arnd Bergmann
2013-04-12 7:50 ` Linus Walleij
2013-04-12 8:08 ` Arnd Bergmann
2013-04-12 8:41 ` Linus Walleij
2013-04-12 10:48 ` Arnd Bergmann [this message]
2013-04-12 13:43 ` Linus Walleij
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=201304121248.54005.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=anmar.oueja@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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.