From: Andrew Lunn <andrew@lunn.ch>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christian Lamparter <chunkeey@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: emac: release DT PHY resources on teardown
Date: Wed, 21 Oct 2026 02:51:38 +0200 [thread overview]
Message-ID: <f4ef98dd-0621-4560-9267-5b8120f9bd20@lunn.ch> (raw)
In-Reply-To: <CAKxU2N9cQjHtoKBLkoOjFQzbz9xzmMQ_UxvXB7g6yvVxK_YKwg@mail.gmail.com>
On Tue, Oct 20, 2026 at 03:37:57PM -0700, Rosen Penev wrote:
> On Tue, Oct 20, 2026 at 3:33 PM <netdev-bot+sinfo@kernel.org> wrote:
> >
> > Hi!
> >
> > This is an automated message. This series looks like a fix, but its
> > commit messages seem to be missing some information:
> >
> > - How the issue was discovered, e.g. hit in production, hit during
> > development, syzbot report, manual code inspection, LLM or static
> > analysis tool scan.
> LLM
Ideally, you should learn from these emails, and put it into the
commit message.
Andrew
next prev parent reply other threads:[~2026-10-21 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 22:30 [PATCH net] net: emac: release DT PHY resources on teardown Rosen Penev
2026-10-20 22:33 ` netdev-bot+sinfo
2026-10-20 22:37 ` Rosen Penev
2026-10-21 0:51 ` Andrew Lunn [this message]
2026-10-21 1:05 ` Andrew Lunn
2026-10-21 3:11 ` Rosen Penev
2026-10-21 13:58 ` Andrew Lunn
2026-10-24 22:42 ` netdev-bot+sashiko
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=f4ef98dd-0621-4560-9267-5b8120f9bd20@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=chunkeey@googlemail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.com \
/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