From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Doug Anderson'" <dianders@chromium.org>,
"'Daniel Kurtz'" <djkurtz@chromium.org>
Cc: "'Russell King'" <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Thomas Abraham'" <thomas.abraham@linaro.org>,
olofj@chromium.org
Subject: RE: [PATCH] ARM: EXYNOS: no duplicate mask/unmask in eint0_15
Date: Thu, 20 Sep 2012 08:59:16 +0900 [thread overview]
Message-ID: <09aa01cd96c2$c6cedd00$546c9700$%kim@samsung.com> (raw)
In-Reply-To: <CAD=FV=UTa4a8wewEdqu=ZnOKe-M5Brv-ex8ZGWfkTb6fqsRB_w@mail.gmail.com>
Doug Anderson wrote:
>
> On Thu, Sep 6, 2012 at 8:21 AM, Daniel Kurtz <djkurtz@chromium.org> wrote:
> > chained_irq_enter/exit() already mask&ack/unmask the chained interrupt.
> > There is no need to also explicitly do it in the handler.
> >
> > Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> > ---
> > arch/arm/mach-exynos/common.c | 7 -------
> > 1 files changed, 0 insertions(+), 7 deletions(-)
> >
> > diff --git a/arch/arm/mach-exynos/common.c b/arch/arm/mach-
> exynos/common.c
> > index 4eb39cd..0a85aec 100644
> > --- a/arch/arm/mach-exynos/common.c
> > +++ b/arch/arm/mach-exynos/common.c
> > @@ -965,14 +965,7 @@ static void exynos_irq_eint0_15(unsigned int irq,
> struct irq_desc *desc)
> > struct irq_chip *chip = irq_get_chip(irq);
> >
> > chained_irq_enter(chip, desc);
> > - chip->irq_mask(&desc->irq_data);
> > -
> > - if (chip->irq_ack)
> > - chip->irq_ack(&desc->irq_data);
> > -
> > generic_handle_irq(*irq_data);
> > -
> > - chip->irq_unmask(&desc->irq_data);
> > chained_irq_exit(chip, desc);
> > }
> >
> > --
> > 1.7.7.3
> >
>
> Acked-by: Doug Anderson <dianders@chromium.org>
Yes, will apply.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2012-09-19 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 15:21 Daniel Kurtz
2012-09-06 15:43 ` Doug Anderson
2012-09-19 23:59 ` Kukjin Kim [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='09aa01cd96c2$c6cedd00$546c9700$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--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=olofj@chromium.org \
--cc=thomas.abraham@linaro.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
all inboxes | Powered by JetHome®