[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230715052517.dinbn25ivsg4ocx2@subtitle>
Date: Sat, 15 Jul 2023 00:25:17 -0500
From: Nishanth Menon <nm@...com>
To: Guenter Roeck <linux@...ck-us.net>
CC: <huaqian.li@...mens.com>, <wim@...ux-watchdog.org>,
<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<conor+dt@...nel.org>, <huaqianlee@...il.com>, <vigneshr@...com>,
<kristo@...nel.org>, <linux-watchdog@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <jan.kiszka@...mens.com>,
<baocheng.su@...mens.com>
Subject: Re: [PATCH v3 2/3] arm64: dts: ti: Add reserved memory for watchdog
On 16:27-20230714, Guenter Roeck wrote:
> On 7/14/23 15:52, Nishanth Menon wrote:
> > On 17:51-20230713, huaqian.li@...mens.com wrote:
> > > From: Li Hua Qian <huaqian.li@...mens.com>
> >
> > I guess I should be explicit about this: Lets keep this dts patch as
> > "DONOTMERGE" in subject line for driver subsystem maintainer (I don't
> > want a repeat of cpufreq maintainers picking up dts and associated
> > warnings that are now pending fixes), resubmit at next rc1 and I can
> > queue up the dts once the maintainers pick up the driver and bindings.
> >
>
> FWIW, I never pick up patches outside drivers/hwmon without explicit Ack
> from responsible maintainers (and most definitely not dts patches unless
> a maintainer responsible for the file(s) specifically asks me to do it
> (which I think never happened).
Oops Guenter, didn't mean to indicate your tree :( -> just wanted
to ensure that developers are clearly aware of what happens with
cross posting series involving multiple maintainers and level set
their expectations. Saves a bunch of private pings later on :)
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists