From: Jakub Kicinski <kuba@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Ravi Gunasekaran <r-gunasekaran@ti.com>,
Neha Malcom Francis <n-francis@ti.com>, <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>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the revision string for J721E
Date: Wed, 18 Oct 2023 10:52:36 -0700 [thread overview]
Message-ID: <20231018105236.347b2354@kernel.org> (raw)
In-Reply-To: <20231018154448.vlunpwbw67xeh4rj@unfasten>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Ravi Gunasekaran <r-gunasekaran@ti.com>,
Neha Malcom Francis <n-francis@ti.com>, <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>
Subject: Re: [PATCH net-next] net: ethernet: ti: davinci_mdio: Fix the revision string for J721E
Date: Wed, 18 Oct 2023 10:52:36 -0700 [thread overview]
Message-ID: <20231018105236.347b2354@kernel.org> (raw)
In-Reply-To: <20231018154448.vlunpwbw67xeh4rj@unfasten>
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?
_______________________________________________
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-18 17:52 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 [this message]
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
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=20231018105236.347b2354@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@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=nm@ti.com \
--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.