From: Mauro Lima <mauro.lima@eclypsium.com>
To: mika.westerberg@linux.intel.com
Cc: broonie@kernel.org, alok.a.tiwari@oracle.com,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Lima <mauro.lima@eclypsium.com>
Subject: [PATCH v2 0/2] spi: intel: PCI driver housekeeping
Date: Wed, 1 Feb 2023 17:54:53 -0300 [thread overview]
Message-ID: <20230201205455.550308-1-mauro.lima@eclypsium.com> (raw)
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
Mauro Lima (2):
spi: intel: Fix device private data and PR_NUM for Broxton controllers
spi: intel: Add support for controllers
drivers/spi/spi-intel-pci.c | 13 ++++++++-----
drivers/spi/spi-intel.c | 2 +-
2 files changed, 9 insertions(+), 6 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-01 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 20:54 Mauro Lima [this message]
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 ` [PATCH v2 0/2] spi: intel: PCI driver housekeeping 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=20230201205455.550308-1-mauro.lima@eclypsium.com \
--to=mauro.lima@eclypsium.com \
--cc=alok.a.tiwari@oracle.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).