From: Andrew Lunn <andrew@lunn.ch>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC net-next] atp: drop ancient parallel port Ethernet driver
Date: Wed, 7 Jan 2026 19:05:41 +0100 [thread overview]
Message-ID: <de684fcb-0520-4e02-a49e-4e422ea13eae@lunn.ch> (raw)
In-Reply-To: <CADkSEUgmpZ4z+erh_VENH0Hp8shF4xUF+Frszfj0Q4YsUnt16g@mail.gmail.com>
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@lunn.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
prev parent reply other threads:[~2026-01-07 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 7:29 [PATCH RFC net-next] atp: drop ancient parallel port Ethernet driver Ethan Nelson-Moore
2026-01-07 17:47 ` Andrew Lunn
2026-01-07 17:59 ` Ethan Nelson-Moore
2026-01-07 18:05 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de684fcb-0520-4e02-a49e-4e422ea13eae@lunn.ch \
--to=andrew@lunn.ch \
--cc=enelsonmoore@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox