From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3256DEB64DD for ; Sat, 24 Jun 2023 15:59:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233224AbjFXP7x convert rfc822-to-8bit (ORCPT ); Sat, 24 Jun 2023 11:59:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54912 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233231AbjFXP7v (ORCPT ); Sat, 24 Jun 2023 11:59:51 -0400 Received: from unicorn.mansr.com (unicorn.mansr.com [81.2.72.234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 317BD1BD2; Sat, 24 Jun 2023 08:59:49 -0700 (PDT) Received: from raven.mansr.com (raven.mansr.com [IPv6:2001:8b0:ca0d:1::3]) by unicorn.mansr.com (Postfix) with ESMTPS id 1C3CE15360; Sat, 24 Jun 2023 16:59:47 +0100 (BST) Received: by raven.mansr.com (Postfix, from userid 51770) id 0FE5B219FD1; Sat, 24 Jun 2023 16:59:47 +0100 (BST) From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Simon Horman Cc: Andrew Lunn , Jeroen Hofstee , Tony Lindgren , netdev@vger.kernel.org, Mugunthan V N , Grygorii Strashko , "open list:TI ETHERNET SWITCH DRIVER (CPSW)" , open list Subject: Re: [PATCH v2] net: cpsw: fix obtaining mac address for am3517 References: <1477668756-2651-1-git-send-email-jhofstee@victronenergy.com> <20161028155213.2t3nwwe3lqaynaer@atomide.com> <20161028181914.mskebckucukzhxhz@atomide.com> <675a346b-faed-4e86-87e7-b332da540055@lunn.ch> Date: Sat, 24 Jun 2023 16:59:47 +0100 In-Reply-To: (Simon Horman's message of "Sat, 24 Jun 2023 17:53:36 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Simon Horman writes: > On Sat, Jun 24, 2023 at 04:02:07PM +0100, Måns Rullgård wrote: >> Simon Horman 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. > > A long time to be sure. As Andrew explained, the patch is now stale. > It will need to be rebased and reposted in ordered to be considered for > upstream. I already did that, only to get more snark in return. -- Måns Rullgård