linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Anand Gore <anand.gore@broadcom.com>,
	Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: tomer.yacoby@broadcom.com, florian.fainelli@broadcom.com,
	samyon.furman@broadcom.com,
	William Zhang <william.zhang@broadcom.com>,
	kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
	dan.beygelman@broadcom.com,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] [PATCH] dt-bindings: arm: add BCM6878 soc
Date: Thu, 2 Jun 2022 08:38:42 +0200	[thread overview]
Message-ID: <7c8ee58e-1f60-b42f-e6e7-6365ff1209f3@linaro.org> (raw)
In-Reply-To: <20220601112700.v3.2.I383a14e417ffde9d8180ee578abbafdf09141c29@changeid>

On 01/06/2022 20:27, Anand Gore wrote:
> Add BCM6878 SOC device tree description to bcmbca binding document.
> 
> Signed-off-by: Anand Gore <anand.gore@broadcom.com>
> 
> ---
> 
> Changes in v3:
> - Simplify subject line

Thanks, subject is simplified, but you still have two of [PATCH] prefixes...


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>


Best regards,
Krzysztof

  reply	other threads:[~2022-06-02  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 18:27 [PATCH v3 0/3] arm: bcmbca: add bcm6878 soc support Anand Gore
2022-06-01 18:27 ` [PATCH v3 1/3] ARM: dts: add dts files for bcmbca soc 6878 Anand Gore
2022-06-01 18:27 ` [PATCH v3 2/3] [PATCH] dt-bindings: arm: add BCM6878 soc Anand Gore
2022-06-02  6:38   ` Krzysztof Kozlowski [this message]
2022-06-01 18:27 ` [PATCH v3 3/3] MAINTAINERS: add bcm6878 to bcmbca arch entry Anand Gore

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=7c8ee58e-1f60-b42f-e6e7-6365ff1209f3@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dan.beygelman@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=samyon.furman@broadcom.com \
    --cc=tomer.yacoby@broadcom.com \
    --cc=william.zhang@broadcom.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;
as well as URLs for NNTP newsgroup(s).