linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Niklas Schnelle" <schnelle@linux.ibm.com>,
	"Peter Huewe" <peterhuewe@gmx.de>
Cc: <linux-integrity@vger.kernel.org>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] char: tpm: handle HAS_IOPORT dependencies
Date: Thu, 04 Apr 2024 18:19:31 +0300	[thread overview]
Message-ID: <D0BFTX8EX1S9.IDOUIUSJ0W51@kernel.org> (raw)
In-Reply-To: <20240404105840.3396821-2-schnelle@linux.ibm.com>

On Thu Apr 4, 2024 at 1:58 PM EEST, Niklas Schnelle wrote:
> In a future patch HAS_IOPORT=n will disable inb()/outb() and friends at
> compile time. We thus need to add this dependency and ifdef sections of
> code using inb()/outb() as alternative access methods.
>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> Co-developed-by: Arnd Bergmann <arnd@kernel.org>
> Signed-off-by: Arnd Bergmann <arnd@kernel.org>
> Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
> ---
> Note: This patch does not depend any not-yet-mainline HAS_IOPORT changes
> and may be merged via subsystem specific trees at your earliest
> convenience.

Thanks I applied it.

BR, Jarkko

      parent reply	other threads:[~2024-04-04 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 10:58 [PATCH 0/1] char: tpm: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-04 10:58 ` [PATCH 1/1] char: tpm: handle " Niklas Schnelle
2024-04-04 11:17   ` Arnd Bergmann
2024-04-04 15:22     ` Jarkko Sakkinen
2024-04-04 15:41     ` Niklas Schnelle
2024-04-04 15:56       ` Arnd Bergmann
2024-04-05  9:23         ` Niklas Schnelle
2024-04-05 21:02           ` Arnd Bergmann
2024-04-04 15:19   ` Jarkko Sakkinen [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=D0BFTX8EX1S9.IDOUIUSJ0W51@kernel.org \
    --to=jarkko@kernel.org \
    --cc=arnd@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=schnelle@linux.ibm.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).