linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: 李维豪 <cn.liweihao@gmail.com>
Cc: robh@kernel.org, hjc@rock-chips.com, andy.yan@rock-chips.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v1 3/7] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M
Date: Tue, 02 Sep 2025 08:49:29 +0200	[thread overview]
Message-ID: <5052759.PIDvDuAF1L@phil> (raw)
In-Reply-To: <CAPEOAkQYA+XSx9QJSmNFLypH0ifE1jvui=MHiEHZ+5a3SR7=uA@mail.gmail.com>

Hi,

Am Montag, 1. September 2025, 02:17:00 Mitteleuropäische Sommerzeit schrieb 李维豪:
> I actually used script to get the maintainer list, but I was not sure
> whether I should send-to or cc every maintainer, so I consulted the
> AI, and the AI said to try not to do so because it might be considered
> noise email, and only send it to the main maintainers.

please don't top-post :-)
https://docs.kernel.org/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions


> Should I cc all the devicetree maintainers with the next patches?

Looks like we did get an Ack still with even only one maintainer listed,
so don't need a resend ... but yeah, please include people listed as
direct maintainers in the future.

Workflows differ, so when submitting a patch you can't know if maintainers
work from patchwork or directly from their inbox.

So it's safer to include more people than not enough :-)

Some trimming of the list can be done though, for example your drm patches
would list the core drm maintainers who most likely do not really care
about individual driver patches ;-) .

get_maintainers.pl thankfully does list the role, so you can decide based
on that.


Heiko


> Best regards,
> WeiHao
> 
> Heiko Stübner <heiko@sntech.de> 于2025年8月31日周日 23:00写道:
> >
> > Hi,
> > Am Sonntag, 31. August 2025, 12:48:51 Mitteleuropäische Sommerzeit schrieb WeiHao Li:
> > > Add a clock id for mipi dsi reference clock, mipi dsi node used it.
> > >
> > > Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
> >
> > you missed a number of devicetree maintainers, Rob thankfully does
> > not need to do this on his own anymore.
> >
> > so please get the appropriate list of maintainers via scripts/get_maintainer.pl
> >
> > Change itself looks fine though.
> >
> > Heiko
> >
> > > ---
> > >  include/dt-bindings/clock/rk3368-cru.h | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/include/dt-bindings/clock/rk3368-cru.h b/include/dt-bindings/clock/rk3368-cru.h
> > > index ebae3cbf8..b951e2906 100644
> > > --- a/include/dt-bindings/clock/rk3368-cru.h
> > > +++ b/include/dt-bindings/clock/rk3368-cru.h
> > > @@ -72,6 +72,7 @@
> > >  #define SCLK_SFC             126
> > >  #define SCLK_MAC             127
> > >  #define SCLK_MACREF_OUT              128
> > > +#define SCLK_MIPIDSI_24M     129
> > >  #define SCLK_TIMER10         133
> > >  #define SCLK_TIMER11         134
> > >  #define SCLK_TIMER12         135
> > >
> >
> >
> >
> >
> 






  reply	other threads:[~2025-09-02  6:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 10:48 [PATCH v1 0/7] drm/rockchip: Add MIPI DSI support for RK3368 WeiHao Li
2025-08-31 10:48 ` [PATCH v1 1/7] drm/rockchip: dsi: Add " WeiHao Li
2025-09-03 12:07   ` Heiko Stuebner
2025-09-03 13:37     ` 李维豪
2025-08-31 10:48 ` [PATCH v1 2/7] drm/rockchip: vop: add lut_size for RK3368 vop_data WeiHao Li
2025-09-03 12:16   ` Heiko Stuebner
2025-08-31 10:48 ` [PATCH v1 3/7] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M WeiHao Li
2025-08-31 15:00   ` Heiko Stübner
2025-09-01  0:17     ` 李维豪
2025-09-02  6:49       ` Heiko Stuebner [this message]
2025-09-03 13:22         ` 李维豪
2025-09-01 21:32   ` Rob Herring (Arm)
2025-08-31 10:48 ` [PATCH v1 4/7] clk: rockchip: use clock ids for SCLK_MIPIDSI_24M on rk3368 WeiHao Li
2025-08-31 10:48 ` [PATCH v1 5/7] ARM: dts: rockchip: Add display subsystem for RK3368 WeiHao Li
2025-08-31 15:04   ` Heiko Stübner
2025-09-01  0:20     ` 李维豪
2025-08-31 10:48 ` [PATCH v1 6/7] ARM: dts: rockchip: Add D-PHY " WeiHao Li
2025-08-31 15:06   ` Heiko Stübner
2025-09-01  0:33     ` 李维豪
2025-08-31 10:48 ` [PATCH v1 7/7] ARM: dts: rockchip: Add DSI " WeiHao Li
2025-08-31 15:09 ` [PATCH v1 0/7] drm/rockchip: Add MIPI DSI support " Heiko Stübner
2025-09-01  0:46   ` 李维豪
2025-09-02 13:17 ` Rob Herring (Arm)
2025-09-03 12:19 ` (subset) " Heiko Stuebner

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=5052759.PIDvDuAF1L@phil \
    --to=heiko@sntech.de \
    --cc=andy.yan@rock-chips.com \
    --cc=cn.liweihao@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hjc@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).