The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: dongxuyang@eswincomputing.com
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
	huangyifeng@eswincomputing.com, benoit.monin@bootlin.com,
	ningyu@eswincomputing.com, linmin@eswincomputing.com,
	pinkesh.vaghela@einfochips.com,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: clock: Add ESWIN eic7700 HSP clock and reset generator
Date: Tue, 12 May 2026 11:48:09 -0400	[thread overview]
Message-ID: <agNLuSCDlukeVGcS@redhat.com> (raw)
In-Reply-To: <20260512020511.726-1-dongxuyang@eswincomputing.com>

Hi Xuyang,

On Tue, May 12, 2026 at 10:05:11AM +0800, dongxuyang@eswincomputing.com wrote:
> From: Xuyang Dong <dongxuyang@eswincomputing.com>
> 
> Add bindings for the high-speed peripherals clock and reset generator
> on the ESWIN EIC7700 HSP.
> 
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Xuyang Dong <dongxuyang@eswincomputing.com>
> ---
>  .../bindings/clock/eswin,eic7700-hspcrg.yaml  | 63 +++++++++++++++++++
>  MAINTAINERS                                   |  5 +-
>  .../dt-bindings/clock/eswin,eic7700-hspcrg.h  | 33 ++++++++++
>  .../dt-bindings/reset/eswin,eic7700-hspcrg.h  | 21 +++++++
>  4 files changed, 120 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/eswin,eic7700-hspcrg.yaml
>  create mode 100644 include/dt-bindings/clock/eswin,eic7700-hspcrg.h
>  create mode 100644 include/dt-bindings/reset/eswin,eic7700-hspcrg.h

Does the MAINTAINERS file need to be updated for these paths? The entry
in linux-next currently looks like this:

ESWIN EIC7700 CLOCK DRIVER
M:      Yifeng Huang <huangyifeng@eswincomputing.com>
M:      Xuyang Dong <dongxuyang@eswincomputing.com>
S:      Maintained
F:      Documentation/devicetree/bindings/clock/eswin,eic7700-clock.yaml
F:      drivers/clk/eswin/
F:      include/dt-bindings/clock/eswin,eic7700-clock.h

Brian


  reply	other threads:[~2026-05-12 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  2:04 [PATCH v4 0/3] Add driver support for ESWIN EIC7700 HSP clock and reset generator dongxuyang
2026-05-12  2:05 ` [PATCH v4 1/3] dt-bindings: clock: Add ESWIN eic7700 " dongxuyang
2026-05-12 15:48   ` Brian Masney [this message]
2026-05-12 16:40     ` Conor Dooley
2026-05-12 17:27       ` Brian Masney
2026-05-12  2:07 ` [PATCH v4 2/3] clk: eswin: Add eic7700 HSP clock driver Xuyang Dong
2026-05-12 15:45   ` Brian Masney
2026-05-12  2:08 ` [PATCH v4 3/3] reset: eswin: Add eic7700 HSP reset driver dongxuyang

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=agNLuSCDlukeVGcS@redhat.com \
    --to=bmasney@redhat.com \
    --cc=benoit.monin@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dongxuyang@eswincomputing.com \
    --cc=huangyifeng@eswincomputing.com \
    --cc=krzk+dt@kernel.org \
    --cc=linmin@eswincomputing.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=ningyu@eswincomputing.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pinkesh.vaghela@einfochips.com \
    --cc=robh@kernel.org \
    --cc=sboyd@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