From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jason Hsu <jasonhell19@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au, patrick@stwcx.xyz,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: yang.chen@quantatw.com, jerry.lin@quantatw.com
Subject: Re: [PATCH v7 2/2] dt-bindings: arm: aspeed: add Meta Ventura board
Date: Fri, 6 Jun 2025 08:52:51 +0200 [thread overview]
Message-ID: <27c1a3fe-4536-4e6f-a636-ffc0fbd52568@kernel.org> (raw)
In-Reply-To: <20250606025251.887953-3-jasonhell19@gmail.com>
On 06/06/2025 04:52, Jason Hsu wrote:
> Document the new compatibles used on Meta Ventura.
This is not what is happening here.
> Add subject prefix for the patch.
No clue what is "subject prefix" for a patch.
>
> Signed-off-by: Jason Hsu <jasonhell19@gmail.com>
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-06 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 2:52 [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason Hsu
2025-06-06 2:52 ` [PATCH v7 1/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC Jason Hsu
2025-06-06 6:50 ` Krzysztof Kozlowski
2025-06-06 2:52 ` [PATCH v7 2/2] dt-bindings: arm: aspeed: add Meta Ventura board Jason Hsu
2025-06-06 6:52 ` Krzysztof Kozlowski [this message]
2025-06-11 12:16 ` 徐傑生
2025-06-06 13:14 ` [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-06-09 1:32 [PATCH v7 2/2] dt-bindings: arm: aspeed: add Meta Ventura board kernel test robot
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=27c1a3fe-4536-4e6f-a636-ffc0fbd52568@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jasonhell19@gmail.com \
--cc=jerry.lin@quantatw.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=robh@kernel.org \
--cc=yang.chen@quantatw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.