From: Peter Korsgaard <peter@korsgaard.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Andi Shyti <andi.shyti@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Samuel Holland <samuel.holland@sifive.com>,
Gregor Herburger <gregor.herburger@tq-group.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: ocores: convert to ioport_map() for IORESOURCE_IO
Date: Tue, 09 Apr 2024 12:38:11 +0200 [thread overview]
Message-ID: <87zfu2om7g.fsf@48ers.dk> (raw)
In-Reply-To: <20240408092923.2816928-1-arnd@kernel.org> (Arnd Bergmann's message of "Mon, 8 Apr 2024 11:28:36 +0200")
>>>>> "Arnd" == Arnd Bergmann <arnd@kernel.org> writes:
> From: Arnd Bergmann <arnd@arndb.de>
> There is at least one machine that uses this driver but does not
> have support for inb()/outb() instructions.
> Convert this to using ioport_map() so it can build on architectures
> that don't provide these but work correctly on machines that require
> using port I/O.
> Fixes: 53f44c1005ba ("i2c: add HAS_IOPORT dependencies")
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Link:
> https://lore.kernel.org/lkml/CAMuHMdVUQ2WgtpYPYfO2T=itMmZ7w=geREqDtsP8Q3ODh9rxdw@mail.gmail.com/
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Peter Korsgaard <peter@korsgaard.com>
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2024-04-09 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:28 [PATCH] i2c: ocores: convert to ioport_map() for IORESOURCE_IO Arnd Bergmann
2024-04-09 10:38 ` Peter Korsgaard [this message]
2024-04-10 13:31 ` Andi Shyti
2024-04-11 8:07 ` Arnd Bergmann
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=87zfu2om7g.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gregor.herburger@tq-group.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.holland@sifive.com \
--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