From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Chester A. Unal" <chester.a.unal@arinc9.com>,
Daniel Golle <daniel@makrotopia.org>,
"David S. Miller" <davem@davemloft.net>,
DENG Qingfang <dqfext@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Sean Wang <sean.wang@mediatek.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v2 2/3] net: dsa: allow use of phylink managed EEE support
Date: Mon, 10 Feb 2025 12:42:43 +0000 [thread overview]
Message-ID: <Z6n0Qz788I_igV8M@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250210123701.7gdt56l5m6t5c6ge@skbuf>
On Mon, Feb 10, 2025 at 02:37:01PM +0200, Vladimir Oltean wrote:
> On Fri, Feb 07, 2025 at 10:24:27PM +0000, Russell King (Oracle) wrote:
> > You may have noticed that I'm no longer putting as much effort into
> > cover messages - and this is precisely why. I honestly don't see
> > that there's any point in spending much time on cover messages anymore.
>
> I have things to do and places to be, and I'm sure you do too, so
> I won't drag this out more than I need to. I'll just give you one
> self-contained example of what bothers me, from this very thread.
> I'm not even expecting you to change all of a sudden, I know it's hard
> and takes time and a deeper understanding of what is happening.
>
> First of all, if "I tend not to read cover messages" isn't sarcastic
> when you've make it pretty obvious so many times that this is important
> to you, then I don't know what sarcasm is.
Sorry, but I disagree with you on this.
I'm getting tired of having to tip-toe around issues like this, I'm not
going to spend anymore time on this thread.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-02-10 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:08 [PATCH net-next v2 0/3] net: dsa: add support for phylink managed EEE Russell King (Oracle)
2025-02-07 13:09 ` [PATCH net-next v2 1/3] net: phylink: provide phylink_mac_implements_lpi() Russell King (Oracle)
2025-02-07 13:09 ` [PATCH net-next v2 2/3] net: dsa: allow use of phylink managed EEE support Russell King (Oracle)
2025-02-07 15:19 ` Vladimir Oltean
2025-02-07 15:33 ` Russell King (Oracle)
2025-02-07 21:38 ` Vladimir Oltean
2025-02-07 22:24 ` Russell King (Oracle)
2025-02-10 12:37 ` Vladimir Oltean
2025-02-10 12:42 ` Russell King (Oracle) [this message]
2025-02-07 13:09 ` [PATCH net-next v2 3/3] net: dsa: mt7530: convert to phylink managed EEE Russell King (Oracle)
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=Z6n0Qz788I_igV8M@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chester.a.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.