From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Cong Yi <yicong.srfy@foxmail.com>,
andrew@lunn.ch, hkallweit1@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
yicong@kylinos.cn
Subject: Re: [PATCH] net: phylink: Separating two unrelated definitions for improving code readability
Date: Thu, 21 Nov 2024 12:26:44 +0000 [thread overview]
Message-ID: <Zz8nBN6Z8s7OZ7Fe@shell.armlinux.org.uk> (raw)
In-Reply-To: <20241121121548.gcbkhw2aead5hae3@skbuf>
On Thu, Nov 21, 2024 at 02:15:48PM +0200, Vladimir Oltean wrote:
> On Thu, Nov 21, 2024 at 12:11:02PM +0000, Russell King (Oracle) wrote:
> > On Thu, Nov 21, 2024 at 01:52:30PM +0200, Vladimir Oltean wrote:
> > > I don't understand what's to defend about this, really.
> >
> > It's not something I want to entertain right now. I have enough on my
> > plate without having patches like this to deal with. Maybe next year
> > I'll look at it, but not right now.
>
> I can definitely understand the lack of time to deal with trivial
> matters, but I mean, it isn't as if ./scripts/get_maintainer.pl
> drivers/net/phy/phylink.c lists a single person...
Trivial patches have an impact beyond just reviewing the patch. They
can cause conflicts, causing work that's in progress to need extra
re-work.
I have the problems of in-band that I've been trying to address since
April. I have phylink EEE support that I've also been trying to move
forward. However, with everything that has happened this year (first,
a high priority work item, followed by holiday, followed by my eye
operations) I've only _just_ been able to get back to looking at these
issues... meanwhile I see that I'm now being asked for stuff about
stacked PHYs which is also going to impact phylink. Oh, and to top it
off, I've discovered that mainline is broken on my test platform
(IRQ crap) which I'm currently trying to debug what has been broken.
Meaning I'm not working on any phylink stuff right now because of
other people's breakage.
It's just been bit of crap after another after another.
Give me a sodding break.
--
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:[~2024-11-21 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 6:27 [PATCH] net: phylink: Separating two unrelated definitions for improving code readability Cong Yi
2024-11-20 8:48 ` Russell King (Oracle)
2024-11-20 9:46 ` Cong Yi
2024-11-21 10:50 ` Vladimir Oltean
2024-11-21 11:21 ` Russell King (Oracle)
2024-11-21 11:52 ` Vladimir Oltean
2024-11-21 12:11 ` Russell King (Oracle)
2024-11-21 12:15 ` Vladimir Oltean
2024-11-21 12:26 ` Russell King (Oracle) [this message]
2024-11-21 12:47 ` Vladimir Oltean
2024-11-21 12:49 ` Russell King (Oracle)
2024-11-21 12:54 ` Vladimir Oltean
2024-11-21 8:32 ` Paolo Abeni
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=Zz8nBN6Z8s7OZ7Fe@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=yicong.srfy@foxmail.com \
--cc=yicong@kylinos.cn \
/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;
as well as URLs for NNTP newsgroup(s).