netdev - Re: [PATCH RFC net-next] atp: drop ancient parallel port Ethernet driver

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: <CADkSEUgmpZ4z+erh_VENH0Hp8shF4xUF+Frszfj0Q4YsUnt16g@mail.gmail.com>
Date: Wed, 7 Jan 2026 09:59:53 -0800
From: Ethan Nelson-Moore <enelsonmoore@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH RFC net-next] atp: drop ancient parallel port Ethernet driver

On Wed, Jan 7, 2026 at 9:47 AM Andrew Lunn <andrew@...n.ch> wrote:
> Please slow down. Get one patch correctly merged to learn the
> processes. Then move onto the next. All you submissions are broken, so
> you are just wasting everybody's time.

Hi, Andrew,

Sorry about that. Next time I will run get-maintainer and make cover
letters for my patch series.
Is there anything broken about the content/commit messages of my
patches, or just the way in which I sent them?
What should my next steps be regarding these patches? Resending them
with the CCs added would just create noise on the mailing list. Should
I directly forward them to maintainers?

Ethan