[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231018180035.saymfqwc2o3xpdf4@pretense>
Date: Wed, 18 Oct 2023 13:00:35 -0500
From: Nishanth Menon <nm@...com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Ravi Gunasekaran <r-gunasekaran@...com>,
Neha Malcom Francis
<n-francis@...com>, <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>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the
revision string for J721E
On 10:52-20231018, Jakub Kicinski wrote:
> On Wed, 18 Oct 2023 10:44:48 -0500 Nishanth Menon wrote:
> > A) netdev maintainers could provide me an rc1 based immutable tag
>
> FWIW that shouldn't be a problem, assuming my script to do so didn't
> bit rot :)
>
> Does it really have to be rc1 or something more recent would work?
Thanks Jakub. SoC tree needs me to send based off rc1 for new features.
I'd rather not mess with that.
Sure if we are doing an fixes pull, we can figure something out to
sync. rc1 saves us the headache of conflict of me sending a PR merge
while netdev maintainers aren't expecting it to be merged to master
via soc tree.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists