netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Jeroen Hofstee <jhofstee@victronenergy.com>,
	Tony Lindgren <tony@atomide.com>,
	netdev@vger.kernel.org, Mugunthan V N <mugunthanvnm@ti.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
	<linux-omap@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] net: cpsw: fix obtaining mac address for am3517
Date: Sat, 24 Jun 2023 16:02:07 +0100	[thread overview]
Message-ID: <yw1xttuw3nv4.fsf@mansr.com> (raw)
In-Reply-To: <ZJcD4sqqzZCq7Fww@corigine.com> (Simon Horman's message of "Sat, 24 Jun 2023 16:55:30 +0200")

Simon Horman <simon.horman@corigine.com> writes:

> On Fri, Jun 23, 2023 at 11:41:10PM +0200, Andrew Lunn wrote:
>> > > I feel like I am missing something here.
>> > 
>> > That is a weird response, you feel like something is missing
>> 
>> There is. The patch.
>> 
>> Maintainers have a slightly better memory than a goldfish, but given
>> the high volume of patches, we don't remember threads from 2016. Also,
>> all our infrastructure has limited memory, this patch is not in lore,
>> and it is not in patchworks. So in terms of getting merged, it does
>> not exist.
>> 
>> We do however recommend that if a patch has not been merged within 2
>> weeks, it is rebased, any Acked-by: etc tags are added and the patch
>> reposted.
>
> Thanks Andrew, that is also my position.
>
> A ping for a multi-year old patch is unusual (for me).
> I was wondering if there was a back story. I guess not.

The only story here is that I was reviewing the set of patches we apply
to our kernels, and I noticed that this one, judging by the discussion,
should have been applied to some tree or other ages ago.

Now if it takes 6 years to get a one-line patch (a fix for a regression,
no less) accepted, I have better things to spend my time on.

-- 
Måns Rullgård

  reply	other threads:[~2023-06-24 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1477668756-2651-1-git-send-email-jhofstee@victronenergy.com>
2016-10-28 15:52 ` [PATCH v2] net: cpsw: fix obtaining mac address for am3517 Tony Lindgren
2016-10-28 18:17   ` Jeroen Hofstee
2016-10-28 18:19     ` Tony Lindgren
2019-03-01 14:52       ` Måns Rullgård
2023-06-23 14:58       ` Måns Rullgård
2023-06-23 20:14         ` Simon Horman
2023-06-23 21:13           ` Jeroen Hofstee
2023-06-23 21:41             ` Andrew Lunn
2023-06-24 14:55               ` Simon Horman
2023-06-24 15:02                 ` Måns Rullgård [this message]
2023-06-24 15:53                   ` Simon Horman
2023-06-24 15:59                     ` Måns Rullgård

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=yw1xttuw3nv4.fsf@mansr.com \
    --to=mans@mansr.com \
    --cc=andrew@lunn.ch \
    --cc=grygorii.strashko@ti.com \
    --cc=jhofstee@victronenergy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@corigine.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).