devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xuyang Dong <dongxuyang@eswincomputing.com>,
	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: [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller
Date: Fri, 7 Nov 2025 08:04:31 +0100	[thread overview]
Message-ID: <fef8569d-0172-48a6-b2cb-0e9023589ced@kernel.org> (raw)
In-Reply-To: <6d2d7ddb.cbd.19a5cf92465.Coremail.dongxuyang@eswincomputing.com>

On 07/11/2025 07:20, 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.  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.

Please really, really think through my first paragraph. It seems you did
not get the point, but understanding the point is essential for all your
future (and this) upstreaming efforts.

Best regards,
Krzysztof

  reply	other threads:[~2025-11-07  7:04 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 [this message]
2025-11-07  7:35       ` Troy Mitchell
2025-11-07  9:02         ` 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=fef8569d-0172-48a6-b2cb-0e9023589ced@kernel.org \
    --to=krzk@kernel.org \
    --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=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 \
    --cc=troy.mitchell@linux.spacemit.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).