From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Grace Kao <grace.kao@intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2 1/1] pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler
Date: Fri, 17 Apr 2020 16:19:34 +0300 [thread overview]
Message-ID: <CAHp75Ve0yzbXUAehBnKnDUFPeLt=H5bmcH_M_zG4RjEHXAq71A@mail.gmail.com> (raw)
In-Reply-To: <20200417090833.GO2586@lahna.fi.intel.com>
On Fri, Apr 17, 2020 at 12:08 PM Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
>
> On Fri, Apr 17, 2020 at 12:11:54PM +0800, Grace Kao wrote:
> > According to Braswell NDA Specification Update (#557593),
> > concurrent read accesses may result in returning 0xffffffff and write
> > instructions may be dropped. We have an established format for the
> > commit references, i.e.
> > cdca06e4e859 ("pinctrl: baytrail: Add missing spinlock usage in
> > byt_gpio_irq_handler")
> >
> > Signed-off-by: Grace Kao <grace.kao@intel.com>
> > Reported-by: Brian Norris <briannorris@chromium.org>
> > Reviewed-by: Brian Norris <briannorris@chromium.org>
>
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied for fixes, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-04-17 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 3:04 [PATCH v2 1/1] pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler Grace Kao
2020-04-17 3:19 ` Brian Norris
2020-04-17 4:11 ` Grace Kao
2020-04-17 9:08 ` Mika Westerberg
2020-04-17 13:19 ` Andy Shevchenko [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='CAHp75Ve0yzbXUAehBnKnDUFPeLt=H5bmcH_M_zG4RjEHXAq71A@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=briannorris@chromium.org \
--cc=grace.kao@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).