From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: David Wang <David_Wang6097@jabil.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: edward_chen@jabil.com, ben_pai@jabil.com
Subject: Re: [PATCH 3/3] dt-bindings: vendor-prefixes: document jabil vendors for Aspeed BMC boards
Date: Wed, 1 Jun 2022 10:28:47 +0200 [thread overview]
Message-ID: <b6b84d29-fd4c-a7e7-6a8f-db86fc3bdb29@linaro.org> (raw)
In-Reply-To: <20220601080856.1548851-3-David_Wang6097@jabil.com>
On 01/06/2022 10:08, David Wang wrote:
> Depends on Krzysztof Kozlowski's vendor prefix patch
>
> Added Jabil vendor prefix for Aspeed SoC based BMC board manufacturers.
>
> ---
>
> v2
>
> - Change the order of items
This is a v5. Please version your patchset properly.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
We have extensive guide how to send patches, so be sure you read all of
them before posting:
https://elixir.bootlin.com/linux/v5.18.1/source/Documentation/process/submitting-patches.rst
https://elixir.bootlin.com/linux/v5.18.1/source/Documentation/process/development-process.rst
https://elixir.bootlin.com/linux/v5.18.1/source/Documentation/process/5.Posting.rst
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-01 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:08 [PATCH 1/3] ARM: dts: aspeed: Adding Jabil Rubypass BMC David Wang
2022-06-01 8:08 ` [PATCH v5 3/3] dt-bindings: arm: aspeed: document board compatibles David Wang
2022-06-01 8:21 ` Krzysztof Kozlowski
2022-06-01 8:08 ` [PATCH 3/3] dt-bindings: vendor-prefixes: document jabil vendors for Aspeed BMC boards David Wang
2022-06-01 8:28 ` Krzysztof Kozlowski [this message]
2022-06-01 8:29 ` [PATCH 1/3] ARM: dts: aspeed: Adding Jabil Rubypass BMC Krzysztof Kozlowski
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=b6b84d29-fd4c-a7e7-6a8f-db86fc3bdb29@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=David_Wang6097@jabil.com \
--cc=ben_pai@jabil.com \
--cc=devicetree@vger.kernel.org \
--cc=edward_chen@jabil.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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.