From: esben@geanix.com
To: Harini Katakam <harini.katakam@amd.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <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>,
<michal.simek@amd.com>, <radhey.shyam.pandey@amd.com>
Subject: Re: [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver
Date: Thu, 28 Sep 2023 16:46:12 +0200 [thread overview]
Message-ID: <878r8qxsnf.fsf@geanix.com> (raw)
In-Reply-To: <20230920115047.31345-1-harini.katakam@amd.com> (Harini Katakam's message of "Wed, 20 Sep 2023 17:20:47 +0530")
Harini Katakam <harini.katakam@amd.com> writes:
> LL TEMAC IP is no longer supported. Hence add an entry marking the
> driver as obsolete.
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.
/Esben
>
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
> ---
> This is an old driver with no bindings doc and hence the maintainers
> entry does not contain a link to documentation.
> ---
> MAINTAINERS | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3dde038545d8..820a7817f02f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -23696,6 +23696,11 @@ F: Documentation/devicetree/bindings/gpio/xlnx,gpio-xilinx.yaml
> F: drivers/gpio/gpio-xilinx.c
> F: drivers/gpio/gpio-zynq.c
>
> +XILINX LL TEMAC ETHERNET DRIVER
> +L: netdev@vger.kernel.org
> +S: Obsolete
> +F: drivers/net/ethernet/xilinx/ll_temac*
> +
> XILINX PWM DRIVER
> M: Sean Anderson <sean.anderson@seco.com>
> S: Maintained
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: esben@geanix.com
To: Harini Katakam <harini.katakam@amd.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <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>,
<michal.simek@amd.com>, <radhey.shyam.pandey@amd.com>
Subject: Re: [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver
Date: Thu, 28 Sep 2023 16:46:12 +0200 [thread overview]
Message-ID: <878r8qxsnf.fsf@geanix.com> (raw)
In-Reply-To: <20230920115047.31345-1-harini.katakam@amd.com> (Harini Katakam's message of "Wed, 20 Sep 2023 17:20:47 +0530")
Harini Katakam <harini.katakam@amd.com> writes:
> LL TEMAC IP is no longer supported. Hence add an entry marking the
> driver as obsolete.
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.
/Esben
>
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
> ---
> This is an old driver with no bindings doc and hence the maintainers
> entry does not contain a link to documentation.
> ---
> MAINTAINERS | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3dde038545d8..820a7817f02f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -23696,6 +23696,11 @@ F: Documentation/devicetree/bindings/gpio/xlnx,gpio-xilinx.yaml
> F: drivers/gpio/gpio-xilinx.c
> F: drivers/gpio/gpio-zynq.c
>
> +XILINX LL TEMAC ETHERNET DRIVER
> +L: netdev@vger.kernel.org
> +S: Obsolete
> +F: drivers/net/ethernet/xilinx/ll_temac*
> +
> XILINX PWM DRIVER
> M: Sean Anderson <sean.anderson@seco.com>
> S: Maintained
next prev parent reply other threads:[~2023-09-28 14:47 UTC|newest]
Thread overview: 12+ 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-20 11:50 ` Harini Katakam
2023-09-28 14:10 ` patchwork-bot+netdevbpf
2023-09-28 14:10 ` patchwork-bot+netdevbpf
2023-09-28 14:46 ` esben [this message]
2023-09-28 14:46 ` esben
2023-09-29 6:06 ` Michal Simek
2023-09-29 6:06 ` Michal Simek
2023-10-04 14:46 ` Jakub Kicinski
2023-10-04 14:46 ` Jakub Kicinski
2023-10-05 13:12 ` Katakam, Harini
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=878r8qxsnf.fsf@geanix.com \
--to=esben@geanix.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harini.katakam@amd.com \
--cc=harinikatakamlinux@gmail.com \
--cc=jsc@umbraculum.org \
--cc=kuba@kernel.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 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.