From: Florian Fainelli <f.fainelli@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Kamal Dasu <kdasu.kdev@gmail.com>, Ray Jui <ray.jui@broadcom.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: spi: Add compatible string for brcmstb SoCs
Date: Wed, 23 Sep 2020 13:38:55 -0700 [thread overview]
Message-ID: <a1e13626-e87a-8114-74ae-560902ab9551@gmail.com> (raw)
In-Reply-To: <160009511834.5702.10954218363830361529.b4-ty@kernel.org>
On 9/14/20 7:52 AM, Mark Brown wrote:
> On Thu, 10 Sep 2020 08:25:36 -0700, Ray Jui wrote:
>> Add compatible string for brcmstb 7445 SoCs.
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/4] spi: Add compatible string for brcmstb SoCs
> commit: d9f0cf9f1176d36d3824459d5b061f4719fcbb8a
> [2/4] spi: bcm-qspi: Add compatible string for BRCMSTB 7445 SoCs
> commit: e0eeb76b818ad93718f9640b0bdad909b453a3b8
> [3/4] spi: bcm-qspi: Fix probe regression on iProc platforms
> commit: 9a852d44b26f8e60e2ae13df563824c0f8489135
> [4/4] spi: bcm-qspi: Clean up 7425, 7429, and 7435 settings
> commit: 3cf5d198785a6b454e6a97246795b0043aff9ac1
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
Mark, can you also submit "spi: bcm-qspi: Fix probe regression on iProc
platforms" towards Linus because this is a bug fix that is currently
affecting the 5.9 kernel.
Thanks
--
Florian
next prev parent reply other threads:[~2020-09-23 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 15:25 [PATCH 1/4] dt-bindings: spi: Add compatible string for brcmstb SoCs Ray Jui
2020-09-10 15:25 ` [PATCH 2/4] spi: bcm-qspi: Add compatible string for BRCMSTB 7445 SoCs Ray Jui
2020-09-10 18:18 ` Florian Fainelli
2020-09-10 15:25 ` [PATCH 3/4] spi: bcm-qspi: Fix probe regression on iProc platforms Ray Jui
2020-09-10 18:20 ` Florian Fainelli
2020-09-10 15:25 ` [PATCH 4/4] spi: bcm-qspi: Clean up 7425, 7429, and 7435 settings Ray Jui
2020-09-10 18:20 ` Florian Fainelli
2020-09-10 18:18 ` [PATCH 1/4] dt-bindings: spi: Add compatible string for brcmstb SoCs Florian Fainelli
2020-09-14 14:52 ` Mark Brown
2020-09-23 20:38 ` Florian Fainelli [this message]
2020-09-24 11:33 ` Mark Brown
2020-09-24 12:00 ` Mark Brown
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=a1e13626-e87a-8114-74ae-560902ab9551@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kdasu.kdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ray.jui@broadcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox