The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	linux-clk@vger.kernel.org
Cc: 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: Mon, 13 Jan 2025 12:18:47 +0100	[thread overview]
Message-ID: <ebb32bec-3fd4-4129-ab5d-d519b10c4405@kernel.org> (raw)
In-Reply-To: <20250113082818.345939-1-sergio.paracuellos@gmail.com>

On 13/01/2025 09:28, Sergio Paracuellos wrote:
> Add clock missing definitions for RT2880, RT305X, RT3352, RT3383, RT5350,
> MT-7620 and MT-76X8 Ralink SoCs.
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>

1. Please use get_maintainers.
2. What is the point of this? We do not add constants when there are no
users. Commit msg explains here nothing.

> ---
>  include/dt-bindings/clock/mtmips-clk.h | 130 +++++++++++++++++++++++++

Filename matching compatible.

Best regards,
Krzysztof

  reply	other threads:[~2025-01-13 11:18 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 [this message]
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
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=ebb32bec-3fd4-4129-ab5d-d519b10c4405@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