From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: luojiaxing <luojiaxing@huawei.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxarm@openeuler.org
Subject: Re: [Linuxarm] [PATCH for next v1 0/2] gpio: few clean up patches to replace spin_lock_irqsave with spin_lock
Date: Mon, 8 Feb 2021 15:28:44 +0200 [thread overview]
Message-ID: <CAHp75VcpeYpsW6B85F0u=B+GToNh=1fYdRSMeQqE0vOtOdSi8A@mail.gmail.com> (raw)
In-Reply-To: <2b8001bb-0bcd-3fea-e15c-2722e7243209@huawei.com>
On Mon, Feb 8, 2021 at 11:11 AM luojiaxing <luojiaxing@huawei.com> wrote:
>
> Sorry, my operation error causes a patch missing from this patch set. I
> re-send the patch set. Please check the new one.
What is the new one?! You have to give proper versioning and change
log for your series.
> On 2021/2/8 16:56, Luo Jiaxing wrote:
> > There is no need to use API with _irqsave in hard IRQ handler, So replace
> > those with spin_lock.
How do you know that another CPU in the system can't serve the
following interrupt from the hardware at the same time?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-02-08 13:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 8:56 [PATCH for next v1 0/2] gpio: few clean up patches to replace spin_lock_irqsave with spin_lock Luo Jiaxing
2021-02-08 8:56 ` [PATCH for next v1 1/2] gpio: omap: Replace raw_spin_lock_irqsave with raw_spin_lock in omap_gpio_irq_handler() Luo Jiaxing
2021-02-11 18:14 ` Grygorii Strashko
2021-02-11 19:39 ` Arnd Bergmann
2021-02-11 20:16 ` Grygorii Strashko
[not found] ` <a61ef337fd1c4538a47fe855920f95d3@hisilicon.com>
[not found] ` <CAK8P3a3SHQNjF5ZpqHQweG7BQ52Xi1hQKDiMVKq4aNK_7VDw6w@mail.gmail.com>
2021-02-12 10:27 ` [Linuxarm] " Grygorii Strashko
2021-02-12 10:42 ` Song Bao Hua (Barry Song)
2021-02-12 10:57 ` Andy Shevchenko
2021-02-12 11:29 ` Song Bao Hua (Barry Song)
2021-02-12 11:53 ` Grygorii Strashko
2021-02-12 13:12 ` Song Bao Hua (Barry Song)
2021-02-12 14:08 ` Grygorii Strashko
2021-02-12 20:06 ` Song Bao Hua (Barry Song)
2021-02-12 20:23 ` Arnd Bergmann
2021-02-12 20:49 ` Song Bao Hua (Barry Song)
2021-02-12 10:59 ` Arnd Bergmann
2021-02-12 11:35 ` Andy Shevchenko
2021-02-08 9:11 ` [Linuxarm] [PATCH for next v1 0/2] gpio: few clean up patches to replace spin_lock_irqsave with spin_lock luojiaxing
2021-02-08 13:28 ` Andy Shevchenko [this message]
2021-02-09 9:24 ` luojiaxing
2021-02-09 9:42 ` Andy Shevchenko
2021-02-10 3:43 ` luojiaxing
2021-02-10 10:50 ` Andy Shevchenko
2021-02-10 11:50 ` [Linuxarm] " Song Bao Hua (Barry Song)
2021-02-10 14:56 ` Andy Shevchenko
2021-02-10 20:42 ` Song Bao Hua (Barry Song)
2021-02-11 9:58 ` Andy Shevchenko
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='CAHp75VcpeYpsW6B85F0u=B+GToNh=1fYdRSMeQqE0vOtOdSi8A@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=grygorii.strashko@ti.com \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=luojiaxing@huawei.com \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).