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,
Jason Hsu <jason-hsu@quantatw.com>
Subject: Re: [PATCH v5 0/2] Add Meta(Facebook) Ventura BMC(AST2600)
Date: Wed, 27 Nov 2024 19:16:53 +0100 [thread overview]
Message-ID: <d165ed94-4979-46e4-a685-44f4636620b6@kernel.org> (raw)
In-Reply-To: <20241127073409.147714-1-jason-hsu@quantatw.com>
On 27/11/2024 08:34, Jason Hsu wrote:
> Add Linux device tree entry related to Meta(Facebook) Ventura specific
> devices connected to BMC(AST2600) SoC.
>
> ---
> v1:
> 1. Create ventura dts file.
> 2. Add commit msg.
> 3. Use format-patch to generate patch.
> 4. Add subject prefixes matching the subsystem.
> ---
> v2:
> ---
> 1. Modify email content.
> v3:
> ---
> 1. Add mail list.
> v4:
> 1. Apply git send-email --thread option.
> 2. Sort nodes in the dts alphanumerically.
> v5:
> 1. Run scripts/checkpatch.pl and fix reported warnings.
Nothing improved. Do you know how to run checkpatch?
Why did you ignore all other comments?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-27 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 7:34 [PATCH v5 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason Hsu
2024-11-27 7:34 ` [PATCH v5 1/2] dt-bindings: arm: aspeed: add Meta Ventura board Jason Hsu
2024-11-27 16:14 ` Conor Dooley
2024-11-27 18:15 ` Krzysztof Kozlowski
2024-11-27 7:34 ` [PATCH v5 2/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC Jason Hsu
2024-11-27 18:15 ` Krzysztof Kozlowski
2024-11-27 18:16 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-21 12:37 [PATCH v5 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason Hsu
2025-03-21 15:05 ` Rob Herring (Arm)
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=d165ed94-4979-46e4-a685-44f4636620b6@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason-hsu@quantatw.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox