[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4131fd06-0e46-5454-fbdb-85ccabc0e8b0@ti.com>
Date: Thu, 19 Oct 2023 11:11:06 +0530
From: Ravi Gunasekaran <r-gunasekaran@...com>
To: Nishanth Menon <nm@...com>, <kuba@...nel.org>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<rogerq@...com>, <andrew@...n.ch>, <f.fainelli@...il.com>,
<horms@...nel.org>, <linux-omap@...r.kernel.org>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<srk@...com>, Thejasvi Konduru <t-konduru@...com>,
<linux-arm-kernel@...ts.infradead.org>, <u-kumar1@...com>,
Neha Malcom Francis <n-francis@...com>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the
revision string for J721E
Nishanth, Jakub,
On 10/18/23 9:14 PM, Nishanth Menon wrote:
>
> We then have the following steps potentially
>
> Drop the fixes and Maintain both SR2.0 and SR1.0 (add SR1.1) so that
> we can merge the socinfo fixes without breaking bisectability.
I will drop the fixes tag then and maintain SR1.0, SR1.1, SR2.0 for J721E
and mention in the commit msg that this is a preparatory patch to fix the
incorrect revision string generation. And in the next cycle, I will
send out a patch removing the invalid revision IDs.
Ideally I would prefer to do this for all the SoCs, but I would need some
time to compile the list. So for now, I will send a v2 targeting only J721E.
Please let me know your thoughts on this.
>
> Also in the future, please CC me as the reporter and for Soc-fixes
> dependency issues (I am listed in the MAINTAINERS file).
>
Sure.
--
Regards,
Ravi
Powered by blists - more mailing lists