From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"David Howells" <dhowells@redhat.com>,
<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<keyrings@vger.kernel.org>,
"Lino Sanfilippo" <l.sanfilippo@kunbus.com>
Subject: Re: [GIT PULL] tpmdd changes for v6.5-rc7
Date: Sat, 12 Aug 2023 03:28:57 +0300 [thread overview]
Message-ID: <CUQ53HZJ7A8M.1GXKBQ7Q2F52D@suppilovahvero> (raw)
In-Reply-To: <20230812000440.2663553-1-jarkko@kernel.org>
On Sat Aug 12, 2023 at 3:04 AM EEST, Jarkko Sakkinen wrote:
> Merge tag 'mm-hotfixes-stable-2023-08-11-13-44' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2023-08-11 14:19:20 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-v6.5-rc7
>
> for you to fetch changes up to 6aaf663ee04a80b445f8f5abff53cb92cb583c88:
>
> tpm_tis: Opt-in interrupts (2023-08-12 02:36:28 +0300)
>
> ----------------------------------------------------------------
> Hi,
>
> These change the probing and enabling of interrupts advertised by the
> platform firmware (i.e. ACPI, Device Tree) to tpm_tis as an opt-in,
> which can be set from the kernel command-line.
I would add that tpm_tis represents the MMIO path to a TPM chip, and is
only one of the drivers using tpm_tis_core.
Opt-in does not concern any other drivers using IRQs, namely tpm_tis_spi
and synquacer, meaning that Lino's changes are still for profit without
question. They were just scoped wrong.
MMIO is the "PC" thing where it matters least whether you poll or use
irqs.
BR, Jarkko
next prev parent reply other threads:[~2023-08-12 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 0:04 Jarkko Sakkinen
2023-08-12 0:28 ` Jarkko Sakkinen [this message]
2023-08-12 2:55 ` pr-tracker-bot
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=CUQ53HZJ7A8M.1GXKBQ7Q2F52D@suppilovahvero \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®