[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <de684fcb-0520-4e02-a49e-4e422ea13eae@lunn.ch>
Date: Wed, 7 Jan 2026 19:05:41 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Ethan Nelson-Moore <enelsonmoore@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH RFC net-next] atp: drop ancient parallel port Ethernet
driver
On Wed, Jan 07, 2026 at 09:59:53AM -0800, Ethan Nelson-Moore wrote:
> 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?
Please take a look at:
https://docs.kernel.org/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> What should my next steps be regarding these patches?
Work on just one patch. Worth through those two documents, fixup what
you got wrong and submit that one patch.
'b4 prep' is a good tool to use for handling patches.
Andrew
Powered by blists - more mailing lists