From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrew Davis <afd@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: pruss: Deprecate use of this driver
Date: Tue, 26 Mar 2024 06:41:51 +0100 [thread overview]
Message-ID: <2024032631-excursion-opposing-be36@gregkh> (raw)
In-Reply-To: <20240325210045.153827-1-afd@ti.com>
On Mon, Mar 25, 2024 at 04:00:45PM -0500, Andrew Davis wrote:
> This UIO driver was used to control the PRU processors found on various
> TI SoCs. It was created before the Remoteproc framework, but now with
> that we have a standard way to program and manage the PRU processors.
> The proper PRU Remoteproc driver should be used instead of this driver.
> Mark this driver deprecated.
>
> The userspace tools to use this are no longer available, so also remove
> those dead links from the Kconfig description.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> drivers/uio/Kconfig | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/uio/Kconfig b/drivers/uio/Kconfig
> index 2e16c5338e5b1..358dc2d19b885 100644
> --- a/drivers/uio/Kconfig
> +++ b/drivers/uio/Kconfig
> @@ -126,19 +126,13 @@ config UIO_FSL_ELBC_GPCM_NETX5152
> http://www.hilscher.com/netx
>
> config UIO_PRUSS
> - tristate "Texas Instruments PRUSS driver"
> + tristate "Texas Instruments PRUSS driver (DEPRECATED)"
This isn't going to do much, why not just delete the driver entirely if
no one uses it?
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-26 5:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 21:00 [PATCH] uio: pruss: Deprecate use of this driver Andrew Davis
2024-03-26 5:41 ` Greg Kroah-Hartman [this message]
2024-03-26 16:19 ` Robert Nelson
2024-03-26 17:02 ` Andrew Davis
2024-03-26 17:12 ` Greg Kroah-Hartman
2024-03-26 17:32 ` Robert Nelson
2024-03-26 17:34 ` Andrew Davis
2024-03-26 17:36 ` Matthijs van Duin
2024-03-26 17:24 ` Matthijs van Duin
2024-03-26 17:36 ` Andrew Davis
2024-03-26 18:18 ` Matthijs van Duin
2024-04-05 15:39 ` Robert Nelson
2024-04-10 14:47 ` Andrew Davis
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=2024032631-excursion-opposing-be36@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=afd@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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