Linux-Integrity Archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: devicetree@vger.kernel.org, linux-integrity@vger.kernel.org,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: [PATCH v2 0/4] Add missing TPM compatible strings
Date: Sat, 13 Jan 2024 18:10:50 +0100	[thread overview]
Message-ID: <cover.1705140898.git.lukas@wunner.de> (raw)

Dear Jarkko,

you've requested me to resend two patches which add "atmel,attpm20p"
as a compatible string to the dt-bindings and to the driver:

https://lore.kernel.org/all/CY65RSEA4VMD.MXHPX898TSW4@suppilovahvero/

The patches depend on a commit which landed in Linus' tree yesterday,
it consolidates the TPM dt-bindings:

https://git.kernel.org/linus/26c9d152ebf3

So after pulling from Linus, you should be able to apply the enclosed
patches cleanly.

I am also including two patches to add other missing compatible strings
to the driver.  I already submitted them in November and December but
they haven't been picked up yet:

https://lore.kernel.org/all/096e5d9d22eaed0a256d2d9b315a77245bd423c6.1701095446.git.lukas@wunner.de/
https://lore.kernel.org/all/5c92620082189dc4e6be277952d0b46df26a6478.1702811113.git.lukas@wunner.de/

Because all these patches merely add device IDs, I believe they can be
picked up and forwarded to Linus at any time, even outside the merge
window.  (According to Documentation/process/stable-kernel-rules.rst,
patches which "just add a device ID" are eligible for stable and
should thus be fair game for fixes pulls.)

Thank you!

Lukas Wunner (4):
  dt-bindings: tpm: Add compatible string atmel,attpm20p
  tpm_tis_spi: Add compatible string atmel,attpm20p
  tpm_tis: Add compatible string atmel,at97sc3204
  tpm: tis_i2c: Add compatible string nuvoton,npct75x

 Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml | 1 +
 drivers/char/tpm/tpm_tis.c                                 | 1 +
 drivers/char/tpm/tpm_tis_i2c.c                             | 2 ++
 drivers/char/tpm/tpm_tis_spi_main.c                        | 1 +
 4 files changed, 5 insertions(+)

-- 
2.40.1


             reply	other threads:[~2024-01-13 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 17:10 Lukas Wunner [this message]
2024-01-13 17:10 ` [PATCH v2 1/4] dt-bindings: tpm: Add compatible string atmel,attpm20p Lukas Wunner
2024-01-13 21:17   ` Jarkko Sakkinen
2024-01-16 18:37     ` Rob Herring
2024-01-16 18:37   ` Rob Herring
2024-01-13 17:10 ` [PATCH v2 2/4] tpm_tis_spi: " Lukas Wunner
2024-01-13 17:10 ` [PATCH v2 3/4] tpm_tis: Add compatible string atmel,at97sc3204 Lukas Wunner
2024-01-13 21:54   ` Jarkko Sakkinen
2024-01-13 17:10 ` [PATCH v2 4/4] tpm: tis_i2c: Add compatible string nuvoton,npct75x Lukas Wunner
2024-01-13 21:55   ` Jarkko Sakkinen
2024-02-20 10:55 ` [PATCH v2 0/4] Add missing TPM compatible strings Lukas Wunner
2024-02-20 18:06   ` Jarkko Sakkinen
2024-02-20 18:09     ` Jarkko Sakkinen
2024-02-20 18:12       ` Jarkko Sakkinen

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=cover.1705140898.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).