netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
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 14:15:48 +0200	[thread overview]
Message-ID: <20241121121548.gcbkhw2aead5hae3@skbuf> (raw)
In-Reply-To: <Zz8jVmO82CHQe5jR@shell.armlinux.org.uk>

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...

  reply	other threads:[~2024-11-21 12:15 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 [this message]
2024-11-21 12:26               ` Russell King (Oracle)
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=20241121121548.gcbkhw2aead5hae3@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --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).