From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] i2c: add HAS_IOPORT dependencies
Date: Fri, 5 Apr 2024 11:09:02 +0200 [thread overview]
Message-ID: <osgkd7mfd5jhl622hvybsbuaqp7awxcm474zzzlbpxkvxh57l7@hpm37bjuandj> (raw)
In-Reply-To: <20240404143351.3950179-2-schnelle@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
Hi,
On Thu, Apr 04, 2024 at 04:33:51PM +0200, Niklas Schnelle wrote:
> In a future patch HAS_IOPORT=n will disable inb()/outb() and friends at
> compile time. We thus need to add HAS_IOPORT as dependency for those
> drivers using them.
>
> 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>
Basically OK, but I am asking this question since last June because I
couldn't find that information in changelogs:
In RFC v1, you agreed to drop PARPORT [1]. Is there a reason you haven't
done this so far?
[1] https://patchwork.ozlabs.org/project/linux-i2c/patch/20211227164317.4146918-11-schnelle@linux.ibm.com/
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-05 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:33 [PATCH 0/1] i2c: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-04 14:33 ` [PATCH 1/1] i2c: add " Niklas Schnelle
2024-04-05 9:09 ` Wolfram Sang [this message]
2024-04-05 9:31 ` Niklas Schnelle
2024-04-05 10:33 ` Wolfram Sang
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=osgkd7mfd5jhl622hvybsbuaqp7awxcm474zzzlbpxkvxh57l7@hpm37bjuandj \
--to=wsa+renesas@sang-engineering.com \
--cc=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 \
/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).