From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Graeme Gregory <gg@slimlogic.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: I2C dummy, regmap, irq domain issue
Date: Tue, 31 Jul 2012 15:15:56 +0100 [thread overview]
Message-ID: <20120731141555.GT4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5017E789.4010701@slimlogic.co.uk>
On Tue, Jul 31, 2012 at 03:11:21PM +0100, Graeme Gregory wrote:
> - d->domain = irq_domain_add_legacy(map->dev->of_node,
> + d->domain = irq_domain_add_legacy(dev->of_node,
Oh, ick. If we're going to have to do this sort of stuff we should just
pass the of_node in and have done with it.
prev parent reply other threads:[~2012-07-31 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:11 I2C dummy, regmap, irq domain issue Graeme Gregory
2012-07-31 14:15 ` Mark Brown [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=20120731141555.GT4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=benh@kernel.crashing.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.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