From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Raymond Tan" <raymond.tan@intel.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Akhil P Oommen" <quic_akhilpo@quicinc.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
dri-devel@lists.freedesktop.org,
"Stanislaw Gruszka" <stanislaw.gruszka@linux.intel.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Anitha Chrisanthus" <anitha.chrisanthus@intel.com>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Jerome Brunet" <jbrunet@baylibre.com>,
linux-samsung-soc@vger.kernel.org,
"Robert Foss" <rfoss@kernel.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Samuel Holland" <samuel@sholland.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Maíra Canal" <mcanal@igalia.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Kuogee Hsieh" <quic_khsieh@quicinc.com>,
"Xinliang Liu" <xinliang.liu@linaro.org>,
"Danilo Krummrich" <dakr@redhat.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-sunxi@lists.linux.dev, "Rahul T R" <r-ravikumar@ti.com>,
"Raphael Gallais-Pou" <raphael.gallais-pou@foss.st.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
etnaviv@lists.freedesktop.org, "Yuan Can" <yuancan@huawei.com>,
"Inki Dae" <inki.dae@samsung.com>,
"Jessica Zhang" <quic_jesszhan@quicinc.com>,
"Sean Paul" <sean@poorly.run>,
"Johan Hovold" <johan+linaro@kernel.org>,
"Hyun Kwon" <hyun.kwon@xilinx.com>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Seung-Woo Kim" <sw0312.kim@samsung.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
kernel@pengutronix.de, "Alex Deucher" <alexander.deucher@amd.com>,
freedreno@lists.freedesktop.org,
"Claudiu Beznea" <claudiu.beznea@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-aspeed@lists.ozlabs.org,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"John Stultz" <jstultz@google.com>,
"Mihail Atanassov" <mihail.atanassov@arm.com>,
"Liang He" <windhl@126.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
lima@lists.freedesktop.org,
"Chunyan Zhang" <zhang.lyra@gmail.com>,
"Alexey Brodkin" <abrodkin@synopsys.com>,
"Minghao Chi" <chi.minghao@zte.com.cn>,
"Steven Price" <steven.price@arm.com>,
linux-rockchip@lists.infradead.org,
"Ben Skeggs" <bskeggs@redhat.com>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Alain Volmat" <alain.volmat@foss.st.com>,
"Liu Ying" <victor.liu@nxp.com>,
linux-arm-msm@vger.kernel.org,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Wang Jianzheng" <wangjianzheng@vivo.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Boris Brezillon" <bbrezillon@kernel.org>,
"Sandy Huang" <hjc@rock-chips.com>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Brian Starkey" <brian.starkey@arm.com>,
"Karol Herbst" <kherbst@redhat.com>,
"Miaoqian Lin" <linmq006@gmail.com>,
"Stefan Agner" <stefan@agner.ch>,
"Michal Simek" <michal.simek@xilinx.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Rob Herring" <robh@kernel.org>,
"Xinwei Kong" <kong.kongxinwei@hisilicon.com>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Mali DP Maintainers" <malidp@foss.arm.com>,
"Joel Stanley" <joel@jms.id.au>,
nouveau@lists.freedesktop.org, "Orson Zhai" <orsonzhai@gmail.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Chun-Kuang Hu" <chunkuang.hu@kernel.org>,
"Lyude Paul" <lyude@redhat.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Guo Zhengkui" <guozhengkui@vivo.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Alison Wang" <alison.wang@nxp.com>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Paul Cercueil" <paul@crapouillou.net>,
"Tomi Valkeinen" <tomba@kernel.org>,
"Deepak R Varma" <drv@mailo.com>,
"Karol Wachowski" <karol.wachowski@linux.intel.com>,
"Kieran Bingham" <kieran.bingham+renesas@ideasonboard.com>,
"Ricardo Ribalda" <ribalda@chromium.org>,
"Tian Tao" <tiantao6@hisilicon.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
linux-stm32@st-md-mailman.stormreply.com,
"Emma Anholt" <emma@anholt.net>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Doug Anderson" <dianders@chromium.org>,
"Liu Shixin" <liushixin2@huawei.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Laura Nao" <laura.nao@collabora.com>,
"David Airlie" <airlied@gmail.com>, "Marek Vasut" <marex@denx.de>,
linux-renesas-soc@vger.kernel.org,
"Yongqin Liu" <yongqin.liu@linaro.org>,
"Jayshri Pawar" <jpawar@cadence.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Russell King" <linux@armlinux.org.uk>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Qiang Yu" <yuq825@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Melissa Wen" <mwen@igalia.com>,
linux-mediatek@lists.infradead.org,
"Fabio Estevam" <festevam@gmail.com>,
"Laurentiu Palcu" <laurentiu.palcu@oss.nxp.com>,
linux-tegra@vger.kernel.org, "Stephen Boyd" <swboyd@chromium.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Yannick Fertre" <yannick.fertre@foss.st.com>,
linux-mips@vger.kernel.org, "Rob Clark" <robdclark@gmail.com>,
"Philippe Cornu" <philippe.cornu@foss.st.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Jyri Sarha" <jyri.sarha@iki.fi>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: patches dropped from drm-misc-next [Was: Re: [PATCH 00/53] drm: Convert to platform remove callback returning] void
Date: Mon, 19 Jun 2023 15:25:28 +0200 [thread overview]
Message-ID: <CAMuHMdWERLXOa4bQvsb7=gx+Q=Hn8v=XJZxahV0j3Vw1xKUYiQ@mail.gmail.com> (raw)
In-Reply-To: <a6ex232lwyovzzazfh6jfvlwszppr2624czgcc5sa4nthkgecf@asauiw3rf4vi>
Hi Maxime,
CC sfr
On Mon, Jun 19, 2023 at 2:51 PM Maxime Ripard <mripard@kernel.org> wrote:
> On Mon, Jun 19, 2023 at 12:53:42PM +0200, Uwe Kleine-König wrote:
> > On Mon, Jun 19, 2023 at 11:45:37AM +0200, Maxime Ripard wrote:
> > > On Sun, Jun 18, 2023 at 06:29:50PM +0200, Uwe Kleine-König wrote:
> > > > On Sun, Jun 18, 2023 at 04:32:55PM +0200, Maxime Ripard wrote:
> > > > > On Sun, Jun 18, 2023 at 02:39:15PM +0200, Uwe Kleine-König wrote:
> > > > > > On Sat, Jun 17, 2023 at 10:57:23AM -0700, Doug Anderson wrote:
> > > > > > > On Sat, Jun 17, 2023 at 9:15 AM Uwe Kleine-König
> > > > > > > <u.kleine-koenig@pengutronix.de> wrote:
> > > > > > > > Together with the patches that were applied later the topmost commit
> > > > > > > > from this series is c2807ecb5290 ("drm/omap: Convert to platform remove
> > > > > > > > callback returning void"). This commit was part for the following next
> > > > > > > > tags:
> > > > > > > >
> > > > > > > > $ git tag -l --contains c2807ecb5290
> > > > > > > > next-20230609
> > > > > > > > next-20230613
> > > > > > > > next-20230614
> > > > > > > > next-20230615
> > > > > > > >
> > > > > > > > However in next-20230616 they are missing. In next-20230616
> > > > > > > > drm-misc/for-linux-next was cf683e8870bd4be0fd6b98639286700a35088660.
> > > > > > > > Compared to c2807ecb5290 this adds 1149 patches but drops 37 (that are
> > > > > > > > also not included with a different commit id). The 37 patches dropped
> > > > > > > > are 13cdd12a9f934158f4ec817cf048fcb4384aa9dc..c2807ecb5290:
> > > > > > > >
> > > > > > > > $ git shortlog -s 13cdd12a9f934158f4ec817cf048fcb4384aa9dc..c2807ecb5290
> > > > > > > > 1 Christophe JAILLET
> > > > > > > > 2 Jessica Zhang
> > > > > > > > 5 Karol Wachowski
> > > > > > > > 1 Laura Nao
> > > > > > > > 27 Uwe Kleine-König
> > > > > > > > 1 Wang Jianzheng
> > > > > > > >
> > > > > > > >
> > > > > > > > I guess this was done by mistake because nobody told me about dropping
> > > > > > > > my/these patches? Can c2807ecb5290 please be merged into drm-misc-next
> > > > > > > > again?
> > > > > > >
> > > > > > > Actually, it was probably a mistake that these patches got merged to
> > > > > > > linuxnext during the 4 days that you noticed. However, your patches
> > > > > > > aren't dropped and are still present in drm-misc-next.
> > > > > > >
> > > > > > > drm-misc has a bit of a unique model and it's documented fairly well here:
> > > > > > >
> > > > > > > https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html
> > > > > >
> > > > > > Is there a flaw then in this unique model (or its implementation) when
> > > > > > drm-misc/for-linux-next moves in a non-fast-forward manner? This isn't
> > > > > > expected, is it?
> > > > >
> > > > > There's no expectation afaik. Any tree merged in linux-next can be
> > > > > rebased, drop a patch, amend one, etc. without any concern.
> > > >
> > > > I agree that there are no rules broken for a tree that is included in
> > > > next and a maintainer is free to rewrite their tree independant of the
> > > > tree being included in next.
> > > >
> > > > Still I think that shouldn't be used as an excuse.
> > >
> > > As an excuse for what?
> >
> > Just because the rules for trees in next allow the merged branch to be
> > rewritten, shouldn't be used to justify rewriting the branch.
> >
> > IMHO you still should ensure that only commits make it into any next
> > snapshot via your tree before X-rc1 for some X (e.g. v6.5) that you
> > intend to be included in X-rc1.
>
> That's never been a next rule either. Rust support has been in next for
> almost a year without being sent as a PR for example.
https://elixir.bootlin.com/linux/latest/source/Documentation/process/2.Process.rst#L297
"The linux-next tree is, by design, a snapshot of what the mainline
is expected to look like after the next merge window closes."
The general rule for linux-next is that its contents are intended to end
up in the next kernel release, and that it should not contain commits
that are intended for the next-next release, cfr. what Stephen sends
out to new trees:
"You will need to ensure that the patches/commits in your tree/series have
been:
[...]
* destined for the current or next Linux merge window."
and what he requests regularly in his announces, e.g.:
"Please do not add any v6.4 related commits to your linux-next included
branches until after v6.3-rc1 has been released."
AFAIU, the exception to the rule is new, self-contained, and sometimes
controversial development, which may have to cook for a few more cycles,
if it ends up in a PR at all.
> > > > For me, if a maintainer puts some patch into next that's a statement
> > > > saying (approximately) "I think this patch is fine and I intend to
> > > > send it to Linus during the next merge window.".
> > >
> > > I mean, that's what we're saying and doing?
> >
> > No, on 2023-06-09 I assumed that my patches will go into v6.5-rc1 (as it
> > was part of next-20230609). A few days later however the patches were
> > dropped.
> >
> > The two options that would have made the experience smoother for me are:
> >
> > a) keep c2807ecb5290 in next and send it for v6.5-rc1; or
>
> That's not an option. You were simply too late for v6.5-rc1, unless you
> expect us to get rid of timezones and work on week-ends. But surely you
> don't.
I don't think anyone expects you to do that...
> > b) keep c2807ecb5290 in a branch that doesn't result it entering next
> > before v6.5-rc1.
>
> All the drm-misc committers use dim. If that's a concern for you, feel
> free to send a patch addressing this to dim.
So you say this is an issue with the tooling? ;-)
If the tooling breaks the rules, perhaps the tooling should be fixed?
> > > > So my expectation is that if a patch is dropped again from next, there
> > > > was a problem and it would be fair if the maintainer tells the
> > > > author/submitter about this problem and that the patch was dropped.
> > >
> > > But it wasn't dropped,
> >
> > From my POV it was dropped from next as it was part of next between
> > next-20230609 and next-20230615 but not any more since next-20230616.
> > You talk about (not) being dropped from some branch in drm-misc, that's
> > irrelevant for the thing I'm complaining about.
>
> You were never told that they were merged in linux-next, but in
> drm-misc-next. If they did, it's mostly an unfortunate artifact.
>
> We have a documentation that explains the process and how drm-misc-next
> works. If that's still confusing somehow, feel free to amend it to make
> it clearer.
Why that document may apply to drm-misc-next, everything that appears
in linux-next should follow the linux-next process
https://elixir.bootlin.com/linux/latest/source/Documentation/process/2.Process.rst#L256
> > > it's still very much to be sent to Linus during the next merge window.
> >
> > "next merge window" as in the one leading to 6.5-rc1? Either we mean
> > different things when we say "next merge window", or there is a
> > misunderstanding I don't see yet.
>
> Linus doesn't want to receive in a PR patches that haven't been in
> linux-next for at least two weeks. In most cases that's rc6, which means
> that by the time we send our last PR before rc6, the
> next-merge-window-while-still-meeting-Linus-requirements is 6.6.
>
> The rule applies to all trees, and it's why the soc tree also requires
> its submaintainers to submit their PR before -rc6.
Unless there's a very good reason to deviate from that (e.g. a bug fix).
> So yeah, sorry if it was confusing. At the end of the day, it's a
> compromise, and I can't find a better one for everyone involved
> (maintainers, contributors and committers alike) off the top of my head.
As I understand, the main issue Uwe is objecting to, is that his
patches ended up in linux-next first, only to be dropped again from
linux-next later, and that there was no communication about the
latter.
If you're not constantly working on a subsystem, it can be very hard
to keep track of the status of your own drive-by patches. When patches
get applied, appear in linux-next, and disappear from linux-next again
later, it's worse...
Thanks for your understanding!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-06-19 15:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 16:25 [PATCH 00/53] drm: Convert to platform remove callback returning void Uwe Kleine-König
2023-05-07 16:26 ` [PATCH 43/53] drm/sun4i: " Uwe Kleine-König
2023-05-08 7:06 ` [PATCH 00/53] drm: " Thomas Zimmermann
2023-05-08 7:50 ` Uwe Kleine-König
2023-05-15 7:50 ` Inki Dae
2023-05-15 9:20 ` Uwe Kleine-König
2023-06-01 15:40 ` Uwe Kleine-König
2023-06-08 16:08 ` Doug Anderson
2023-06-08 16:26 ` Laurent Pinchart
2023-06-08 16:47 ` Doug Anderson
2023-06-08 17:19 ` Tomi Valkeinen
2023-06-08 17:38 ` Doug Anderson
2023-06-17 16:12 ` patches dropped from drm-misc-next [Was: Re: [PATCH 00/53] drm: Convert to platform remove callback returning] void Uwe Kleine-König
2023-06-17 16:51 ` Chen-Yu Tsai
2023-06-17 17:57 ` Doug Anderson
2023-06-18 12:39 ` Uwe Kleine-König
2023-06-18 14:02 ` Uwe Kleine-König
2023-06-18 14:32 ` Maxime Ripard
2023-06-18 16:29 ` Uwe Kleine-König
2023-06-19 9:45 ` Maxime Ripard
2023-06-19 10:53 ` Uwe Kleine-König
2023-06-19 12:47 ` Maxime Ripard
2023-06-19 13:25 ` Geert Uytterhoeven [this message]
2023-06-19 14:02 ` Maxime Ripard
2023-06-19 14:20 ` Geert Uytterhoeven
2023-06-19 13:58 ` Uwe Kleine-König
2023-09-09 14:37 ` [PATCH 00/53] drm: Convert to platform remove callback returning void Javier Martinez Canillas
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='CAMuHMdWERLXOa4bQvsb7=gx+Q=Hn8v=XJZxahV0j3Vw1xKUYiQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=abrodkin@synopsys.com \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=alexander.deucher@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=alison.wang@nxp.com \
--cc=andersson@kernel.org \
--cc=andrew@aj.id.au \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=anitha.chrisanthus@intel.com \
--cc=arnd@arndb.de \
--cc=baolin.wang@linux.alibaba.com \
--cc=bbrezillon@kernel.org \
--cc=brian.starkey@arm.com \
--cc=broonie@kernel.org \
--cc=bskeggs@redhat.com \
--cc=chi.minghao@zte.com.cn \
--cc=christian.gmeiner@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=chunkuang.hu@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=drv@mailo.com \
--cc=emma@anholt.net \
--cc=etnaviv@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=freedreno@lists.freedesktop.org \
--cc=guozhengkui@vivo.com \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=hyun.kwon@xilinx.com \
--cc=inki.dae@samsung.com \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=jbrunet@baylibre.com \
--cc=jernej.skrabec@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=joel@jms.id.au \
--cc=johan+linaro@kernel.org \
--cc=jonas@kwiboo.se \
--cc=jonathanh@nvidia.com \
--cc=jpawar@cadence.com \
--cc=jstultz@google.com \
--cc=jyri.sarha@iki.fi \
--cc=karol.wachowski@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=kherbst@redhat.com \
--cc=khilman@baylibre.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=kyungmin.park@samsung.com \
--cc=l.stach@pengutronix.de \
--cc=laura.nao@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=lima@lists.freedesktop.org \
--cc=linmq006@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-imx@nxp.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liushixin2@huawei.com \
--cc=liviu.dudau@arm.com \
--cc=lyude@redhat.com \
--cc=malidp@foss.arm.com \
--cc=marex@denx.de \
--cc=marijn.suijten@somainline.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=matthias.bgg@gmail.com \
--cc=mcanal@igalia.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=mihail.atanassov@arm.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=neil.armstrong@linaro.org \
--cc=nicolas.ferre@microchip.com \
--cc=noralf@tronnes.org \
--cc=nouveau@lists.freedesktop.org \
--cc=orsonzhai@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=paul.kocialkowski@bootlin.com \
--cc=paul@crapouillou.net \
--cc=philippe.cornu@foss.st.com \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_akhilpo@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=r-ravikumar@ti.com \
--cc=raphael.gallais-pou@foss.st.com \
--cc=raymond.tan@intel.com \
--cc=rfoss@kernel.org \
--cc=ribalda@chromium.org \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.org \
--cc=sean@poorly.run \
--cc=sfr@canb.auug.org.au \
--cc=shawnguo@kernel.org \
--cc=stanislaw.gruszka@linux.intel.com \
--cc=stefan@agner.ch \
--cc=steven.price@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=sw0312.kim@samsung.com \
--cc=swboyd@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=tiantao6@hisilicon.com \
--cc=tomba@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=victor.liu@nxp.com \
--cc=ville.syrjala@linux.intel.com \
--cc=wangjianzheng@vivo.com \
--cc=wens@csie.org \
--cc=windhl@126.com \
--cc=xinliang.liu@linaro.org \
--cc=yannick.fertre@foss.st.com \
--cc=yongqin.liu@linaro.org \
--cc=yuancan@huawei.com \
--cc=yuq825@gmail.com \
--cc=zhang.lyra@gmail.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).