public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Xuyang Dong <dongxuyang@eswincomputing.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, bmasney@redhat.com,
	troy.mitchell@linux.spacemit.com, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
	huangyifeng@eswincomputing.com, pinkesh.vaghela@einfochips.com
Subject: Re: Re: [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller
Date: Fri, 7 Nov 2025 15:35:47 +0800	[thread overview]
Message-ID: <1618037D174FDF5F+aQ2hU1J9oLEKCq25@kernel.org> (raw)
In-Reply-To: <6d2d7ddb.cbd.19a5cf92465.Coremail.dongxuyang@eswincomputing.com>

Hi Xuyang,

On Fri, Nov 07, 2025 at 02:20:23PM +0800, Xuyang Dong wrote:
> > > 
> > >   Gentle ping. Looking forward to your reply. Thank you very much!
> > 
> > Please do not top post.
> > 
> > You did not add any maintainers of these drivers, so I would not put it
> > high on our priority list. 
Do you have any plans to become a maintainer? If so, this patch might get
reviewed with higher priority. I think that's what Krzysztof meant.

                              - Troy
> >
> > Ask yourself - why would community
> > maintainer like to take unmaintained driver? So the community maintainer
> > would maintain, right? To add him more work? If that is the case, isn't
> > better not to take the driver? You see where I am getting at?
> > 
> > Also, I don't see any involvement in reviews from eswin. The only
> > reviews here where from DT maintainers, Troy and Brian (I hope I did not
> > miss anyone), so again - you just put all the effort on us and then ping
> > us...
> > 
> 
> Hello Krzysztof Brian Troy,
> 
> Would you kindly review the updated v7 patches at your earliest convenience?
> 
> Thanks to Krzysztof for your reply.
> 
> These patches have already undergone review within our internal team. 
> The reason for adding eswin maintainers to the mailing list is to ensure 
> that these colleagues can promptly receive community feedback and stay 
> informed of the discussions.
> 
> Regards,
> Xuyang Dong

  parent reply	other threads:[~2025-11-07  7:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  7:16 [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller dongxuyang
2025-10-23  7:17 ` [PATCH v7 1/2] dt-bindings: clock: eswin: Documentation for eic7700 SoC dongxuyang
2025-11-07  7:46   ` Troy Mitchell
2025-10-23  7:18 ` [PATCH v7 2/2] clock: eswin: Add eic7700 clock driver dongxuyang
2025-11-07  7:44   ` Troy Mitchell
2025-11-11  1:21     ` Xuyang Dong
2025-11-11  3:38       ` Troy Mitchell
2025-11-06  7:57 ` [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller Xuyang Dong
2025-11-06  8:20   ` Krzysztof Kozlowski
2025-11-07  6:20     ` Xuyang Dong
2025-11-07  7:04       ` Krzysztof Kozlowski
2025-11-07  7:35       ` Troy Mitchell [this message]
2025-11-07  9:02         ` Re: " Xuyang Dong
2025-11-07 10:05           ` Troy Mitchell
2025-11-07 15:54             ` Troy Mitchell

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=1618037D174FDF5F+aQ2hU1J9oLEKCq25@kernel.org \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dongxuyang@eswincomputing.com \
    --cc=huangyifeng@eswincomputing.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=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