From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 3/3] mfd: arizona: Use arizona_map_irq instead of hard coding it
Date: Tue, 22 Nov 2016 16:07:59 +0000 [thread overview]
Message-ID: <20161122160759.GB1867@localhost.localdomain> (raw)
In-Reply-To: <20161122155436.GF10134@dell.home>
On Tue, Nov 22, 2016 at 03:54:36PM +0000, Lee Jones wrote:
> On Tue, 22 Nov 2016, Lee Jones wrote:
>
> > On Mon, 14 Nov 2016, Charles Keepax wrote:
> >
> > > We have arizona_map_irq we might as well use it rather than hard coding
> > > it in several places.
> > >
> > > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > > ---
> > > drivers/mfd/arizona-irq.c | 21 +++++++++------------
> > > 1 file changed, 9 insertions(+), 12 deletions(-)
> >
> > Applied, thanks.
>
> Slight change of plan.
>
> Patch doesn't seem to apply.
>
> Please rebase it on top of my MFD tree and resubmit.
>
Yeah depends on the first patch, ignore the ones I just sent
(since I had assumed you fixed that up manually) and I will
resend the whole series.
Thanks,
Charles
next prev parent reply other threads:[~2016-11-22 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 17:15 [PATCH v2 1/3] mfd: arizona: Correctly clean up after IRQs Charles Keepax
2016-11-14 17:15 ` [PATCH 2/3] mfd: arizona: Disable IRQs during driver remove Charles Keepax
2016-11-22 12:59 ` Lee Jones
2016-11-14 17:15 ` [PATCH 3/3] mfd: arizona: Use arizona_map_irq instead of hard coding it Charles Keepax
2016-11-22 13:01 ` Lee Jones
2016-11-22 15:54 ` Lee Jones
2016-11-22 16:07 ` Charles Keepax [this message]
2016-11-22 12:57 ` [PATCH v2 1/3] mfd: arizona: Correctly clean up after IRQs Lee Jones
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=20161122160759.GB1867@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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