From: Jakub Kicinski <kuba@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: <esben@geanix.com>, Harini Katakam <harini.katakam@amd.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<jsc@umbraculum.org>, <christophe.jaillet@wanadoo.fr>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <harinikatakamlinux@gmail.com>,
<radhey.shyam.pandey@amd.com>
Subject: Re: [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver
Date: Wed, 4 Oct 2023 07:46:46 -0700 [thread overview]
Message-ID: <20231004074646.6fd564a6@kernel.org> (raw)
In-Reply-To: <4b8361e5-08f8-4cf8-a277-769647fb9c4c@amd.com>
On Fri, 29 Sep 2023 08:06:46 +0200 Michal Simek wrote:
> > Ok. But while that might mean that no new designs should use LL TEMAC
> > IP, why do we need to declare the driver for it obsolete?
> >
> > Existing designs using LL TEMAC IP might need to upgrade Linux kernel
> > also.
>
> If you want to take responsibility for keeping that driver alive then feel free
> to send a patch on the top and declare it publicly. We are not able to test it
> on these old platforms that's why we are publicly saying that it is end of us.
Why Obsolete tho? There's no other driver for this IP, so Orphan sounds
more accurate. Please change it to Orphan.
_______________________________________________
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-04 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:50 [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver Harini Katakam
2023-09-28 14:10 ` patchwork-bot+netdevbpf
2023-09-28 14:46 ` esben
2023-09-29 6:06 ` Michal Simek
2023-10-04 14:46 ` Jakub Kicinski [this message]
2023-10-05 13:12 ` Katakam, Harini
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=20231004074646.6fd564a6@kernel.org \
--to=kuba@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=esben@geanix.com \
--cc=harini.katakam@amd.com \
--cc=harinikatakamlinux@gmail.com \
--cc=jsc@umbraculum.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).