From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, Kamal Dasu <kdasu.kdev@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
yendapally.reddy@broadcom.com, f.fainelli@gmail.com
Subject: Re: [PATCH 0/3] spi-bcm-qspi spcr3 enahancements
Date: Mon, 11 Oct 2021 18:01:38 +0100 [thread overview]
Message-ID: <163397094904.6819.8623150916603608652.b4-ty@kernel.org> (raw)
In-Reply-To: <20211008203603.40915-1-kdasu.kdev@gmail.com>
On Fri, 8 Oct 2021 16:36:00 -0400, Kamal Dasu wrote:
> This change set feature enahancements for spcr3 transfer modes as well as
> adds support for half-duplex 3-wire mode transfer.
>
> Kamal Dasu (3):
> spi: bcm-qspi: Add mspi spcr3 32/64-bits xfer mode
> spi: bcm-qspi: clear MSPI spifie interrupt during probe
> spi: bcm-qspi: add support for 3-wire mode for half duplex transfer
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] spi: bcm-qspi: Add mspi spcr3 32/64-bits xfer mode
commit: ee4d62c47326c69e57180da53c057e55f0e73e35
[2/3] spi: bcm-qspi: clear MSPI spifie interrupt during probe
commit: 75b3cb97eb1f05042745c0655a7145b0262d4c5c
[3/3] spi: bcm-qspi: add support for 3-wire mode for half duplex transfer
commit: e81cd07dcf50ef4811f6667dba89c5614278cbdd
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.
Thanks,
Mark
prev parent reply other threads:[~2021-10-11 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 20:36 [PATCH 0/3] spi-bcm-qspi spcr3 enahancements Kamal Dasu
2021-10-08 20:36 ` [PATCH 1/3] spi: bcm-qspi: Add mspi spcr3 32/64-bits xfer mode Kamal Dasu
2021-10-11 2:54 ` Florian Fainelli
2021-10-08 20:36 ` [PATCH 2/3] spi: bcm-qspi: clear MSPI spifie interrupt during probe Kamal Dasu
2021-10-11 2:53 ` Florian Fainelli
2021-10-11 12:15 ` Mark Brown
2021-10-08 20:36 ` [PATCH 3/3] spi: bcm-qspi: add support for 3-wire mode for half duplex transfer Kamal Dasu
2021-10-11 2:54 ` Florian Fainelli
2021-10-11 17:01 ` Mark Brown [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=163397094904.6819.8623150916603608652.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=yendapally.reddy@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).