From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
linux-spi@vger.kernel.org, Pratyush Yadav <p.yadav@ti.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.17 34/49] spi: cadence-quadspi: fix protocol setup for non-1-1-X operations
Date: Sun, 17 Apr 2022 17:33:28 -0400 [thread overview]
Message-ID: <YlyHqKVBC9u1F9xS@sashalap> (raw)
In-Reply-To: <YlVrbR6Giy2OXe1R@sirena.org.uk>
On Tue, Apr 12, 2022 at 01:07:09PM +0100, Mark Brown wrote:
>On Tue, Apr 12, 2022 at 01:49:19PM +0200, Matthias Schiffer wrote:
>
>Please don't top post, reply in line with needed context. This allows
>readers to readily follow the flow of conversation and understand what
>you are talking about and also helps ensure that everything in the
>discussion is being addressed.
>
>> what's your plan regarding this patch and the other patch I sent [1]? I
>> think there has been some confusion regarding which solution we want to
>> backport to stable kernels (well, at least I'm confused...)
>
>Well, it's up to the stable people what they choose to backport -
>they're generally fairly aggressive about what they pick up so I guess
>they want to take this one?
>
>> I'm fine with this patch getting backported, but in that case [1]
>> doesn't make sense anymore (in fact I expected this patch to be dropped
>> for now when I submitted [1], due to Pratyush Yadav's concerns).
>
>> [1] https://patchwork.kernel.org/project/spi-devel-general/patch/20220406132832.199777-1-matthias.schiffer@ew.tq-group.com/
>
>For the benefit of those playing at home that's "spi: cadence-quadspi:
>fix incorrect supports_op() return value". It's much more the sort of
>thing I'd expect to see backported to stable so it seems good from that
>point of view.
I'm a bit confused as I don't see the other patch in Linus's tree?
I'll queue this one up then...
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-04-17 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220412004411.349427-1-sashal@kernel.org>
2022-04-12 0:43 ` [PATCH AUTOSEL 5.17 34/49] spi: cadence-quadspi: fix protocol setup for non-1-1-X operations Sasha Levin
2022-04-12 11:49 ` Matthias Schiffer
2022-04-12 12:07 ` Mark Brown
2022-04-17 21:33 ` Sasha Levin [this message]
2022-04-19 13:15 ` Mark Brown
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=YlyHqKVBC9u1F9xS@sashalap \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=p.yadav@ti.com \
--cc=stable@vger.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