From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Frank.Li@oss.nxp.com, Mark Brown <broonie@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Radu Pirea <radu_nicolae.pirea@upb.ro>,
CL Wang <cl634@andestech.com>,
Ryan Wanner <ryan.wanner@microchip.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Vladimir Oltean <olteanv@gmail.com>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Han Xu <han.xu@nxp.com>,
Haibo Chen <haibo.chen@nxp.com>,
Linus Walleij <linusw@kernel.org>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Heiko Stuebner <heiko@sntech.de>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Andi Shyti <andi.shyti@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Yixun Lan <dlan@kernel.org>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Alain Volmat <alain.volmat@foss.st.com>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
"moderated list:ARM/Microchip (AT91) SoC support"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"open list:FREESCALE DSPI DRIVER" <imx@lists.linux.dev>,
"open list:ARM/QUALCOMM MAILING LIST"
<linux-arm-msm@vger.kernel.org>,
"open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>,
"open list:RENESAS RZ/V2H(P) RSPI DRIVER"
<linux-renesas-soc@vger.kernel.org>,
"open list:SAMSUNG SPI DRIVERS"
<linux-samsung-soc@vger.kernel.org>,
"open list:RISC-V SPACEMIT SoC Support"
<linux-riscv@lists.infradead.org>,
"open list:RISC-V SPACEMIT SoC Support"
<spacemit@lists.linux.dev>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
"open list:ARM/Allwinner sunXi SoC support"
<linux-sunxi@lists.linux.dev>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v2 1/1] spi: use dmaengine_desc_set_callback()
Date: Mon, 9 Nov 2026 23:10:38 +0100 [thread overview]
Message-ID: <78833267-f204-4387-9f8c-c7e0d5df59a5@kernel.org> (raw)
In-Reply-To: <avIJhv7p2v30U8H9@ashevche-desk.local>
On 09/11/2026 18:57, Andy Shevchenko wrote:
> On Fri, Nov 06, 2026 at 08:20:33AM +0100, Krzysztof Kozlowski wrote:
>>>>
>>>> Statement of oversight DOES NOT include "part of the patch".
>>>
>>> So, it means I MUST from now on REQUIRE a split before reviewing.
>>> Right?
>>
>> Why "from now on"? The reviewer's statement of oversight is worded like
>> that since beginning? Also nothing stops you from reviewing parts. We
>> discuss the statement of oversight and its result: giving Rb tag. The Rb
>> tag is not output of some review, but agreement with statement of
>> oversight and performing what is stated there.
>>
>> You can review parts, but you do not provide Rb tag.
>
> No, I'm not going to review something that I may not put Rb tag on.
> I can NAK or ignore (or Ack without viewing, but it equals to ignore to me).
That's your call, but you put it on yourself, so do not blame us for "I
MUST from now on REQUIRE"...
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-09 22:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:22 Frank.Li
2026-11-04 16:57 ` Andy Shevchenko
2026-11-04 17:02 ` Krzysztof Kozlowski
2026-11-04 17:08 ` Krzysztof Kozlowski
2026-11-04 17:23 ` Andy Shevchenko
2026-11-04 17:27 ` Krzysztof Kozlowski
2026-11-04 20:41 ` Andy Shevchenko
2026-11-04 22:54 ` Krzysztof Kozlowski
2026-11-05 9:04 ` Andy Shevchenko
2026-11-05 9:07 ` Krzysztof Kozlowski
2026-11-05 9:10 ` Wolfram Sang
2026-11-05 9:36 ` Andy Shevchenko
2026-11-05 9:45 ` Wolfram Sang
2026-11-05 10:06 ` Andy Shevchenko
2026-11-05 9:34 ` Andy Shevchenko
2026-11-06 7:20 ` Krzysztof Kozlowski
2026-11-09 17:57 ` Andy Shevchenko
2026-11-09 22:10 ` Krzysztof Kozlowski [this message]
2026-11-09 22:41 ` Andy Shevchenko
2026-11-04 17:25 ` Krzysztof Kozlowski
2026-11-04 20:44 ` Andy Shevchenko
2026-11-04 23:02 ` Krzysztof Kozlowski
2026-11-05 9:01 ` Andy Shevchenko
2026-11-05 9:03 ` Andy Shevchenko
2026-11-05 9:16 ` Geert Uytterhoeven
2026-11-04 18:18 ` Florian Fainelli
2026-11-05 9:20 ` Geert Uytterhoeven
2026-11-05 9:24 ` Krzysztof Kozlowski
2026-11-07 14:51 ` 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=78833267-f204-4387-9f8c-c7e0d5df59a5@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=cl634@andestech.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=daniel@zonque.org \
--cc=dlan@kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=festevam@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=haibo.chen@nxp.com \
--cc=han.xu@nxp.com \
--cc=haojian.zhuang@gmail.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=heiko@sntech.de \
--cc=imx@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=ldewangan@nvidia.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=nicolas.ferre@microchip.com \
--cc=olteanv@gmail.com \
--cc=peter.griffin@linaro.org \
--cc=radu_nicolae.pirea@upb.ro \
--cc=rjui@broadcom.com \
--cc=robert.jarzmik@free.fr \
--cc=ryan.wanner@microchip.com \
--cc=s.hauer@pengutronix.de \
--cc=samuel@sholland.org \
--cc=sbranden@broadcom.com \
--cc=skomatineni@nvidia.com \
--cc=spacemit@lists.linux.dev \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.com \
--cc=troy.mitchell@linux.spacemit.com \
--cc=tudor.ambarus@linaro.org \
--cc=wens@kernel.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®