[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJcD4sqqzZCq7Fww@corigine.com>
Date: Sat, 24 Jun 2023 16:55:30 +0200
From: Simon Horman <simon.horman@...igine.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Jeroen Hofstee <jhofstee@...tronenergy.com>,
Måns Rullgård <mans@...sr.com>,
Tony Lindgren <tony@...mide.com>, netdev@...r.kernel.org,
Mugunthan V N <mugunthanvnm@...com>,
Grygorii Strashko <grygorii.strashko@...com>,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)" <linux-omap@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] net: cpsw: fix obtaining mac address for am3517
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.
Powered by blists - more mailing lists