Linux clock framework development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
	mturquette@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, yangshiji66@outlook.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: add clock definitions for Ralink SoCs
Date: Wed, 15 Jan 2025 09:27:34 +0100	[thread overview]
Message-ID: <10e21109-f4fa-42f5-a3fa-c6fa67fba783@kernel.org> (raw)
In-Reply-To: <CAMhs-H9+hHnQQ3PSs2fCNvwdoJhrteARXQutFiziGN9+TFAgrw@mail.gmail.com>

On 14/01/2025 08:43, Sergio Paracuellos wrote:
>>
>>> consumer nodes. So if adding this header is not a possibility with the
>>> changes in the yaml file I will forget about this addition and this
>>> patch.
>>
>> Header without user is pointless. Driver and the DTS are the expected users.
> 
> Understood. So having only DTSs as users is not a possible way to go.
> It is clear now. Forget about this patch then.

Only DTS user, with a justification, would go. Then just resend this
patch when you have at least DTS user.

Best regards,
Krzysztof

  reply	other threads:[~2025-01-15  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  8:28 [PATCH] dt-bindings: clock: add clock definitions for Ralink SoCs Sergio Paracuellos
2025-01-13 11:18 ` Krzysztof Kozlowski
2025-01-13 11:32   ` Sergio Paracuellos
2025-01-13 12:17     ` Krzysztof Kozlowski
2025-01-13 12:29       ` Sergio Paracuellos
2025-01-13 12:37         ` Krzysztof Kozlowski
2025-01-13 12:58           ` Sergio Paracuellos
2025-01-14  7:09             ` Krzysztof Kozlowski
2025-01-14  7:43               ` Sergio Paracuellos
2025-01-15  8:27                 ` Krzysztof Kozlowski [this message]
2025-01-15  9:00                   ` Sergio Paracuellos

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=10e21109-f4fa-42f5-a3fa-c6fa67fba783@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=yangshiji66@outlook.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