From: Will Deacon <will.deacon@arm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Andy Gross <andy.gross@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [Patch v4 2/2] firmware: qcom: scm: Fix interrupted SCM calls
Date: Tue, 31 Jan 2017 14:45:39 +0000 [thread overview]
Message-ID: <20170131144539.GE22283@arm.com> (raw)
In-Reply-To: <CAOesGMhRS8hmHqO=T6X3nooztqhwRO_YMDe2F960TnED-tJN-w@mail.gmail.com>
On Mon, Jan 30, 2017 at 10:22:18PM -0800, Olof Johansson wrote:
> On Mon, Jan 30, 2017 at 2:55 AM, Will Deacon <will.deacon@arm.com> wrote:
> > On Sun, Jan 29, 2017 at 04:24:51PM -0800, Olof Johansson wrote:
> >> Seems like a more appropriate change than burden all platforms with
> >> longer code path due to your quirk.
> >
> > I really don't think it's a problem. Do you have numbers suggesting
> > otherwise?
>
> Not on this first quirk, no.
>
> Anyway, I guess I'm just bikeshedding. You should merge this code if
> you're happy with it.
Ok. Andy, does it work for you if I take these two patches via arm64? I'll
need Russell's ack on the arch/arm/ part.
Will
next prev parent reply other threads:[~2017-01-31 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 16:58 [Patch v4 0/2] Support ARM SMCC SoC vendor quirks Andy Gross
2017-01-19 16:58 ` [Patch v4 1/2] arm: kernel: Add SMC structure parameter Andy Gross
2017-01-19 16:58 ` [Patch v4 2/2] firmware: qcom: scm: Fix interrupted SCM calls Andy Gross
2017-01-30 0:24 ` Olof Johansson
2017-01-30 10:55 ` Will Deacon
2017-01-31 6:22 ` Olof Johansson
2017-01-31 14:45 ` Will Deacon [this message]
2017-01-31 16:03 ` Andy Gross
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=20170131144539.GE22283@arm.com \
--to=will.deacon@arm.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=olof@lixom.net \
/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).