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]
Message-ID: <20211028083211.2c0cb03f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Thu, 28 Oct 2021 08:32:11 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Cc:     "jan.kundrat@...net.cz" <jan.kundrat@...net.cz>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
        "Brelinski, Tony" <tony.brelinski@...el.com>
Subject: Re: [PATCH net-next 3/4] igb: unbreak I2C bit-banging on i350

On Thu, 28 Oct 2021 15:25:55 +0000 Nguyen, Anthony L wrote:
> On Wed, 2021-10-27 at 09:30 -0700, Jakub Kicinski wrote:
> > On Mon, 25 Oct 2021 10:55:07 -0700 Tony Nguyen wrote:  
> > > From: Jan Kundrát <jan.kundrat@...net.cz>
> > > 
> > > The driver tried to use Linux' native software I2C bus master
> > > (i2c-algo-bits) for exporting the I2C interface that talks to the
> > > SFP
> > > cage(s) towards userspace. As-is, however, the physical SCL/SDA
> > > pins
> > > were not moving at all, staying at logical 1 all the time.  
> > 
> > So targeting net-next because this never worked?  
> 
> Correct. Would you prefer I send this patch via net instead?

I think net-next will be fine here. Only patch 1 needs rejigging then.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ