From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andi Shyti" <andi.shyti@kernel.org>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Peter Korsgaard" <peter@korsgaard.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"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: Thu, 11 Apr 2024 10:07:30 +0200 [thread overview]
Message-ID: <5f99920d-0c9c-4921-ab85-e5bca11c2da6@app.fastmail.com> (raw)
In-Reply-To: <cwbht6xtv2nfqm7xz2ra52dtfwx3whjyyigbxxtdrwzcsq3llp@vhryqiyrjxqx>
On Wed, Apr 10, 2024, at 15:31, Andi Shyti wrote:
> Hi Arnd,
>
> On Mon, Apr 08, 2024 at 11:28:36AM +0200, Arnd Bergmann wrote:
>> 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")
>
> I had to update this Fixes tag as I have done a rebase.
>
Ok, thanks for merging.
In case you do another rebase, you could also move this patch
ahead of the other one to avoid adding and then removing the
dependency again.
Arnd
prev parent reply other threads:[~2024-04-11 8:07 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
2024-04-10 13:31 ` Andi Shyti
2024-04-11 8:07 ` Arnd Bergmann [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=5f99920d-0c9c-4921-ab85-e5bca11c2da6@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--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=peter@korsgaard.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).