From: Nishanth Menon <nm@ti.com>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <rogerq@ti.com>, <andrew@lunn.ch>,
<f.fainelli@gmail.com>, <horms@kernel.org>,
<linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <srk@ti.com>,
Thejasvi Konduru <t-konduru@ti.com>,
<linux-arm-kernel@lists.infradead.org>, <u-kumar1@ti.com>,
Neha Malcom Francis <n-francis@ti.com>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the revision string for J721E
Date: Thu, 19 Oct 2023 12:23:49 -0500 [thread overview]
Message-ID: <20231019172349.mwtxt5he222d6zrj@engraved> (raw)
In-Reply-To: <4131fd06-0e46-5454-fbdb-85ccabc0e8b0@ti.com>
On 11:11-20231019, Ravi Gunasekaran wrote:
> 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.
just do the full list in one shot. it is easier that way than having to
repeat this sync over and over again.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <rogerq@ti.com>, <andrew@lunn.ch>,
<f.fainelli@gmail.com>, <horms@kernel.org>,
<linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <srk@ti.com>,
Thejasvi Konduru <t-konduru@ti.com>,
<linux-arm-kernel@lists.infradead.org>, <u-kumar1@ti.com>,
Neha Malcom Francis <n-francis@ti.com>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the revision string for J721E
Date: Thu, 19 Oct 2023 12:23:49 -0500 [thread overview]
Message-ID: <20231019172349.mwtxt5he222d6zrj@engraved> (raw)
In-Reply-To: <4131fd06-0e46-5454-fbdb-85ccabc0e8b0@ti.com>
On 11:11-20231019, Ravi Gunasekaran wrote:
> 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.
just do the full list in one shot. it is easier that way than having to
repeat this sync over and over again.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-19 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 14:00 [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the revision string for J721E Ravi Gunasekaran
2023-10-18 15:44 ` Nishanth Menon
2023-10-18 15:44 ` Nishanth Menon
2023-10-18 17:52 ` Jakub Kicinski
2023-10-18 17:52 ` Jakub Kicinski
2023-10-18 18:00 ` Nishanth Menon
2023-10-18 18:00 ` Nishanth Menon
2023-10-18 18:16 ` Jakub Kicinski
2023-10-18 18:16 ` Jakub Kicinski
2023-10-19 5:41 ` Ravi Gunasekaran
2023-10-19 5:41 ` Ravi Gunasekaran
2023-10-19 17:23 ` Nishanth Menon [this message]
2023-10-19 17:23 ` Nishanth Menon
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=20231019172349.mwtxt5he222d6zrj@engraved \
--to=nm@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@ti.com \
--cc=srk@ti.com \
--cc=t-konduru@ti.com \
--cc=u-kumar1@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.