public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	 Niklas Schnelle <schnelle@linux.ibm.com>
Cc: linux-i2c@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
	 Heiko Carstens <hca@linux.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] i2c: Handle HAS_IOPORT dependencies
Date: Sat, 06 Apr 2024 21:49:08 +0200	[thread overview]
Message-ID: <171243294822.75370.15549035576290413403.b4-ty@kernel.org> (raw)
In-Reply-To: <20240405101009.2807447-1-schnelle@linux.ibm.com>

Hi

On Fri, 05 Apr 2024 12:10:08 +0200, Niklas Schnelle wrote:
> This is a follow up in my ongoing effort of making inb()/outb() and
> similar I/O port accessors compile-time optional. Previously I sent this
> as a treewide series titled "treewide: Remove I/O port accessors for
> HAS_IOPORT=n" with the latest being its 5th version[0]. With a significant
> subset of patches merged I've changed over to per-subsystem series. These
> series are stand alone and should be merged via the relevant tree such
> that with all subsystems complete we can follow this up with the final
> patch that will make the I/O port accessors compile-time optional.
> 
> [...]

Applied to i2c/i2c-host on

git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Thank you,
Andi

Patches applied
===============
[1/1] i2c: add HAS_IOPORT dependencies
      commit: 53f44c1005ba64215ab6c3c5bbbcaef0870ae7d6


      parent reply	other threads:[~2024-04-06 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 10:10 [PATCH v2 0/1] i2c: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-05 10:10 ` [PATCH v2 1/1] i2c: add " Niklas Schnelle
2024-04-05 10:32   ` Wolfram Sang
2024-04-08  8:50   ` Geert Uytterhoeven
2024-04-08  9:30     ` Arnd Bergmann
2024-04-06 19:49 ` Andi Shyti [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=171243294822.75370.15549035576290413403.b4-ty@kernel.org \
    --to=andi.shyti@kernel.org \
    --cc=arnd@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schnelle@linux.ibm.com \
    --cc=wsa+renesas@sang-engineering.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