devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <rafal@milecki.pl>,
	"William Zhang" <william.zhang@broadcom.com>
Cc: Linux ARM List <linux-arm-kernel@lists.infradead.org>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.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 v2 1/2] arm64: dts: broadcom: bcm4908: Fix timer node for BCM4906 SoC
Date: Wed, 13 Jul 2022 09:29:56 -0700	[thread overview]
Message-ID: <5bab132b-d6e2-045d-3960-0ece99da9723@gmail.com> (raw)
In-Reply-To: <50bd9abda381ebdcaea41d116b4baa9c@milecki.pl>

On 7/12/22 23:49, Rafał Miłecki wrote:
> On 2022-07-08 20:25, William Zhang wrote:
>> The cpu mask value in interrupt property inherits from bcm4908.dtsi
>> which sets to four cpus. Correct the value to two cpus for dual core
>> BCM4906 SoC.
>>
>> Fixes: c8b404fb05dc ("arm64: dts: broadcom: bcm4908: add BCM4906
>> Netgear R8000P DTS files")
> 
> Well, one note. You shouldn't line break Fixes: line.

Took care of that before applying the two patches:

https://github.com/torvalds/linux/commit/b4a544e415e9be33b37d9bfa9d9f9f4d13f553d6

https://github.com/torvalds/linux/commit/8bd582ae9a71d7f14c4e0c735b2eacaf7516d626
-- 
Florian

      reply	other threads:[~2022-07-13 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 18:25 [PATCH v2 1/2] arm64: dts: broadcom: bcm4908: Fix timer node for BCM4906 SoC William Zhang
2022-07-08 18:25 ` [PATCH v2 2/2] arm64: dts: broadcom: bcm4908: Fix cpu node for smp boot William Zhang
2022-07-08 19:45   ` Florian Fainelli
2022-07-08 19:45 ` [PATCH v2 1/2] arm64: dts: broadcom: bcm4908: Fix timer node for BCM4906 SoC Florian Fainelli
2022-07-13  6:47 ` Rafał Miłecki
2022-07-13  6:49 ` Rafał Miłecki
2022-07-13 16:29   ` Florian Fainelli [this message]

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=5bab132b-d6e2-045d-3960-0ece99da9723@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --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).