lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 05 Apr 2024 11:31:55 +0200
From: Niklas Schnelle <schnelle@...ux.ibm.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Andi Shyti <andi.shyti@...nel.org>, linux-i2c@...r.kernel.org,
        Arnd
 Bergmann <arnd@...nel.org>, Heiko Carstens <hca@...ux.ibm.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] i2c: add HAS_IOPORT dependencies

On Fri, 2024-04-05 at 11:09 +0200, Wolfram Sang wrote:
> 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@...nel.org>
> > Signed-off-by: Arnd Bergmann <arnd@...nel.org>
> > Signed-off-by: Niklas Schnelle <schnelle@...ux.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?

Only reasons seems to be that I'm bad at juggling large patch series.
i2c-partport.c builds fine with HAS_IOPORT=n and I don't see a reason
why it wouldn't work with MMIO based parallel port drivers.

Will send a v2 shortly.

Thanks,
Niklas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ