From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Golle <daniel@makrotopia.org>,
stable@vger.kernel.org
Subject: Re: [net PATCH 2/2] net: phy: Skip PHY LEDs OF registration for Generic PHY driver
Date: Fri, 4 Oct 2024 16:12:44 +0200 [thread overview]
Message-ID: <66fff7e3.df0a0220.275e8c.fc30@mx.google.com> (raw)
In-Reply-To: <ce1feaa5-b9e0-4245-8e64-6e90bcf528eb@lunn.ch>
On Fri, Oct 04, 2024 at 04:11:22PM +0200, Andrew Lunn wrote:
> > Ok I will squash this and the net-next patch and change to dbg.
> >
> > Do you think it's still "net" content? I'm more tempted to post in
> > net-next since I have to drop the Generic PHY condition.
>
> Does it cause real problems for users? That is the requirement for
> stable.
>
Not strictly bugs or kernel panic, just annoyance, ok will post to
net-next.
--
Ansuel
next prev parent reply other threads:[~2024-10-04 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 22:10 [net PATCH 1/2] net: phy: Remove LED entry from LEDs list on unregister Christian Marangi
2024-10-03 22:10 ` [net PATCH 2/2] net: phy: Skip PHY LEDs OF registration for Generic PHY driver Christian Marangi
2024-10-03 22:50 ` Andrew Lunn
2024-10-04 9:13 ` Christian Marangi
2024-10-04 13:44 ` Andrew Lunn
2024-10-04 13:46 ` Christian Marangi
2024-10-04 14:11 ` Andrew Lunn
2024-10-04 14:12 ` Christian Marangi [this message]
2024-10-03 22:45 ` [net PATCH 1/2] net: phy: Remove LED entry from LEDs list on unregister Andrew Lunn
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=66fff7e3.df0a0220.275e8c.fc30@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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