From: Mark Brown <broonie@kernel.org>
To: mika.westerberg@linux.intel.com, Mauro Lima <mauro.lima@eclypsium.com>
Cc: alok.a.tiwari@oracle.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] spi: intel: PCI driver housekeeping
Date: Thu, 02 Feb 2023 14:59:57 +0000 [thread overview]
Message-ID: <167534999769.359854.6364951616234994334.b4-ty@kernel.org> (raw)
In-Reply-To: <20230201205455.550308-1-mauro.lima@eclypsium.com>
On Wed, 01 Feb 2023 17:54:53 -0300, Mauro Lima wrote:
> Found some controllers' private data that were wrong according
> to the documentation. Also, the number of Protected Regions from
> Broxton types was changed.
> The second patch adds more Device IDs to the module table.
> Probably good candidates to stable?
>
> Changes since v1:
> * Change BXT to Broxton in commit message
> * Sort new Device IDs by hex value in the driver's module table
> * Add ack from Mika Westerberg to the first patch
> Link: https://lore.kernel.org/r/20230201050455.505135-1-mauro.lima@eclypsium.com
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: intel: Fix device private data and PR_NUM for Broxton controllers
commit: b4c58d540777124f31ab0cb37a14c6573438d381
[2/2] spi: intel: Add support for controllers
commit: 7c62a2279b9e88f2cbfa3b92dc49c8b7806c56f8
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:[~2023-02-02 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 20:54 Mauro Lima
2023-02-01 20:54 ` [PATCH v2 1/2] spi: intel: Fix device private data and PR_NUM for Broxton controllers Mauro Lima
2023-02-01 20:54 ` [PATCH v2 2/2] spi: intel: Add support for controllers Mauro Lima
2023-02-02 5:33 ` Mika Westerberg
2023-02-02 15:01 ` [External] : " ALOK TIWARI
2023-02-02 14:59 ` 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=167534999769.359854.6364951616234994334.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mauro.lima@eclypsium.com \
--cc=mika.westerberg@linux.intel.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
all inboxes | Powered by JetHome®