From: Andrew Lunn <andrew@lunn.ch>
To: tresonic <tresonic@mail.de>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org, regressions@lists.linux.dev,
rmk+kernel@armlinux.org.uk, kuba@kernel.org
Subject: Re: [REGRESSION][BISECTED] stmmac: suspend hangs since 1b9707e6f1a9 ("net: stmmac: enable RPS and RBU interrupts")
Date: Sat, 18 Jul 2026 16:11:40 +0200 [thread overview]
Message-ID: <36957839-b03a-4403-b08e-12bbadd8bc0c@lunn.ch> (raw)
In-Reply-To: <54128253-eb77-48f5-a673-94fb65edb78f@mail.de>
> Sorry for the noob question, how would I submit this fix?
There are two documents for you to read:
https://docs.kernel.org/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
Since this is a fix, please use the net tree. And include a Fixes: tag
indicating the patch which broke it.
> Just commit and separately git send-email to netdev@vger.kernel.org?
./scripts/get_maintainer.pl will give you a list of email addresses.
Or take a look at
https://b4.docs.kernel.org/en/latest/contributor/prep.html
b4 automates some of the steps in producing patches, keeping track of
versions, working out who to send to etc.
Often with the kernel, the code is easy. Getting the processes correct
is harder. But we are here to help.
Andrew
next prev parent reply other threads:[~2026-07-18 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 20:10 [REGRESSION][BISECTED] stmmac: suspend hangs since 1b9707e6f1a9 ("net: stmmac: enable RPS and RBU interrupts") tresonic
2026-07-16 21:47 ` Andrew Lunn
2026-07-17 7:18 ` tresonic
2026-07-17 15:40 ` Andrew Lunn
2026-07-17 22:23 ` tresonic
2026-07-17 22:34 ` tresonic
2026-07-18 0:16 ` Andrew Lunn
2026-07-18 7:35 ` tresonic
2026-07-18 13:11 ` Maxime Chevallier
2026-07-18 13:32 ` tresonic
2026-07-18 14:11 ` Andrew Lunn [this message]
2026-07-18 15:32 ` tresonic
2026-07-18 14:06 ` Andrew Lunn
2026-07-18 15:27 ` [PATCH] net: stmmac: dwmac4: mask interrupts before stopping DMA in suspend Luis Lang
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=36957839-b03a-4403-b08e-12bbadd8bc0c@lunn.ch \
--to=andrew@lunn.ch \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tresonic@mail.de \
/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