From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Mark Brown <broonie@kernel.org>, Michael Walle <mwalle@kernel.org>
Cc: linux-spi@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: Fix error code checking in spi_mem_exec_op()
Date: Wed, 13 Mar 2024 10:45:33 -0700 [thread overview]
Message-ID: <2645c7c4-8140-4e2e-9ad6-faefc92b5873@broadcom.com> (raw)
In-Reply-To: <7109907f-baf3-47e2-b33f-3403e1299176@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
On 3/13/24 10:40, Mark Brown wrote:
> On Wed, Mar 13, 2024 at 06:33:43PM +0100, Michael Walle wrote:
>
>> FWIW in next, there is commit
>> e63aef9c9121e ("spi: spi-mem: add statistics support to ->exec_op() calls")
>> that probably will conflict with this one.
>
> Indeed, this doesn't apply - please fix and resend.
Will do, and will also strip the Change-Id tag that sneaked through.
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2024-03-13 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 17:10 [PATCH] spi: Fix error code checking in spi_mem_exec_op() Florian Fainelli
2024-03-13 17:33 ` Michael Walle
2024-03-13 17:40 ` Mark Brown
2024-03-13 17:45 ` Florian Fainelli [this message]
2024-03-13 19:03 ` Florian Fainelli
2024-03-14 12:58 ` Mark Brown
2024-03-13 18:28 ` Pratyush Yadav
2024-03-13 18:37 ` Florian Fainelli
2024-03-13 19:29 ` Pratyush Yadav
2024-03-13 19:34 ` Florian Fainelli
2024-03-13 20:06 ` Florian Fainelli
2024-03-13 21:15 ` Pratyush Yadav
2024-03-15 17:13 ` 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=2645c7c4-8140-4e2e-9ad6-faefc92b5873@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=acelan.kao@canonical.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@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