linux-kernel - Re: [PATCH v3] tulip: convert to devres

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] [day] [month] [year] [list]

Message-ID: <20220519090817.3187b659@kernel.org>
Date:   Thu, 19 May 2022 09:08:17 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Rolf Eike Beer <eike-kernel@...tec.de>
Cc:     patchwork-bot+netdevbpf@...nel.org, linux-kernel@...r.kernel.org,
        linux-parisc@...r.kernel.org, netdev@...r.kernel.org,
        yangyingliang@...wei.com, davem@...emloft.net, edumazet@...gle.com
Subject: Re: [PATCH v3] tulip: convert to devres

On Thu, 19 May 2022 15:40:44 +0200 Rolf Eike Beer wrote:
> Works fine on my HP C3600:
> 
> [  274.452394] tulip0: no phy info, aborting mtable build
> [  274.499041] tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1
> [  274.750691] net eth0: Digital DS21142/43 Tulip rev 65 at MMIO 0xf4008000, 00:30:6e:08:7d:21, IRQ 17
> [  283.104520] net eth0: Setting full-duplex based on MII#1 link partner capability of c1e1
> 
> Signed-off-by: Rolf Eike Beer <eike-kernel@...tec.de>
> ---
>  drivers/net/ethernet/dec/tulip/eeprom.c     |  7 ++-
>  drivers/net/ethernet/dec/tulip/tulip_core.c | 64 ++++++---------------
>  2 files changed, 20 insertions(+), 51 deletions(-)
> 
> v2: rebased
> 
> v3: fixed typo in variable for CONFIG_GSC code

Thanks for following up. Unfortunately net-next is "stable" in terms of
commits it contains, we can swap the old patch for the new one. You
need to send an incremental change.

Please provide a Fixes tag, and if you prefer to reply to something
with the patch please reply to the report of breakage, that's better
context for this work. Or just post independently (which is generally
recommended)