From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Tomasz Figa <t.figa@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Grant Likely <grant.likely@linaro.org>,
Jiri Kosina <jkosina@suse.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Masanari Iida <standby24x7@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
rtc-linux@googlegroups.com, Russell King <linux@arm.linux.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 1/3] mfd: Add irq domain support for max8998 interrupts
Date: Fri, 21 Jun 2013 14:12:02 +0000 [thread overview]
Message-ID: <u0l61x7a6z1.fsf@orc04.imf.au.dk> (raw)
In-Reply-To: <1371818017-5215-2-git-send-email-t.figa@samsung.com> (Tomasz Figa's message of "Fri, 21 Jun 2013 14:33:35 +0200")
Tomasz Figa <t.figa@samsung.com> writes:
> All uses of irq_base in platform data and max8997 driver private data
> are removed.
>
[...]
> +static int max8998_irq_domain_map(struct irq_domain *d, unsigned int irq,
> + irq_hw_number_t hw)
> +{
> + struct max8997_dev *max8998 = d->host_data;
I may be wrong, but this sure looks like a typo (or copy-pasto).
--
Rasmus Villemoes
<http://rasmusvillemoes.dk/>
next prev parent reply other threads:[~2013-06-21 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:33 [PATCH v2 0/3] regulator: max8998: Add support for Device Tree Tomasz Figa
2013-06-21 12:33 ` [PATCH v2 1/3] mfd: Add irq domain support for max8998 interrupts Tomasz Figa
2013-06-21 14:12 ` Rasmus Villemoes [this message]
2013-06-21 14:31 ` Mark Brown
2013-06-21 12:33 ` [PATCH v2 2/3] regulator: max8998: Use arrays for specifying voltages in platform data Tomasz Figa
2013-06-21 14:39 ` Mark Brown
2013-06-21 12:33 ` [PATCH v2 3/3] mfd: max8998: Add support for Device Tree Tomasz Figa
2013-06-21 14:37 ` Mark Brown
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=u0l61x7a6z1.fsf@orc04.imf.au.dk \
--to=linux@rasmusvillemoes.dk \
--cc=a.zummo@towertech.it \
--cc=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=jkosina@suse.cz \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=standby24x7@gmail.com \
--cc=t.figa@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®