From: Kukjin Kim <kgene@kernel.org>
To: 'Mark Brown' <broonie@kernel.org>,
'Charles Keepax' <ckeepax@opensource.wolfsonmicro.com>
Cc: kgene@kernel.org, linux@arm.linux.org.uk, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: RE: [PATCH] ARM: S3C64XX: Use fixed IRQ bases to avoid conflicts on Cragganmore
Date: Tue, 24 Mar 2015 22:03:20 +0900 [thread overview]
Message-ID: <02e801d06632$e75527e0$b5ff77a0$@kernel.org> (raw)
In-Reply-To: <20150322160316.GB6643@sirena.org.uk>
Mark Brown wrote:
>
> On Sun, Mar 22, 2015 at 10:40:41AM +0000, Charles Keepax wrote:
> > There are two PMICs on Cragganmore, currently one dynamically assign
> > its IRQ base and the other uses a fixed base. It is possible for the
> > statically assigned PMIC to fail if its IRQ is taken by the dynamically
> > assigned one. Fix this by statically assigning both the IRQ bases.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
>
> Reviwed-by: Mark Brown <broonie@kernel.org>
>
Thanks for your review.
> This probably wants to go to stable as well.
OK, I'll.
Thanks,
Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Use fixed IRQ bases to avoid conflicts on Cragganmore
Date: Tue, 24 Mar 2015 22:03:20 +0900 [thread overview]
Message-ID: <02e801d06632$e75527e0$b5ff77a0$@kernel.org> (raw)
In-Reply-To: <20150322160316.GB6643@sirena.org.uk>
Mark Brown wrote:
>
> On Sun, Mar 22, 2015 at 10:40:41AM +0000, Charles Keepax wrote:
> > There are two PMICs on Cragganmore, currently one dynamically assign
> > its IRQ base and the other uses a fixed base. It is possible for the
> > statically assigned PMIC to fail if its IRQ is taken by the dynamically
> > assigned one. Fix this by statically assigning both the IRQ bases.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
>
> Reviwed-by: Mark Brown <broonie@kernel.org>
>
Thanks for your review.
> This probably wants to go to stable as well.
OK, I'll.
Thanks,
Kukjin
next prev parent reply other threads:[~2015-03-24 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 10:40 [PATCH] ARM: S3C64XX: Use fixed IRQ bases to avoid conflicts on Cragganmore Charles Keepax
2015-03-22 10:40 ` Charles Keepax
2015-03-22 16:03 ` Mark Brown
2015-03-22 16:03 ` Mark Brown
2015-03-24 13:03 ` Kukjin Kim [this message]
2015-03-24 13:03 ` Kukjin Kim
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='02e801d06632$e75527e0$b5ff77a0$@kernel.org' \
--to=kgene@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.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=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 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.