From: Greg KH <gregkh@linuxfoundation.org>
To: Grewstad <dogestad24@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
jic23@kernel.org, jacobsfeder@gmail.com,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, hjk@hansjkoch.de,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [RFC] drivers/staging/axis-fifo: TODO file and subsystem direction
Date: Tue, 2 Jun 2026 08:45:32 +0200 [thread overview]
Message-ID: <2026060203-protozoan-widow-1b41@gregkh> (raw)
In-Reply-To: <CAD03fjaHmsYpLj_PU48AW7h=E6XdMpqKsS7wQtDQKnEkGpa93g@mail.gmail.com>
On Tue, Jun 02, 2026 at 12:07:48PM +0530, Grewstad wrote:
> On Tue, Jun 2, 2026 at 11:28 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > If no one is using it, why don't we just delete it then? It can come
> > back if someone shows a real use-case for it.
>
> Yes, this is what i was thinking. These boards are generally used for
> development and research teams can probably maintain a patch if
> they really want it. As you said, it can always come back if a
> user-space application depends on it.
>
> One drawback that comes to mind is a development group may
> currently be maintaining a proprietary application that depends on it.
Then they will speak up when the driver goes away and we can revert the
removal quite easily. It's not like code is ever "gone" for forever.
thanks,
greg k-h
prev parent reply other threads:[~2026-06-02 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 14:50 [RFC] drivers/staging/axis-fifo: TODO file and subsystem direction Grewstad
2026-05-31 15:25 ` Greg KH
2026-06-01 5:39 ` Grewstad
2026-06-01 5:53 ` Greg KH
2026-05-31 19:52 ` Andrew Lunn
2026-06-01 6:05 ` Grewstad
2026-06-01 12:29 ` Andrew Lunn
2026-06-01 16:45 ` Grewstad
2026-06-02 5:57 ` Greg KH
2026-06-02 6:37 ` Grewstad
2026-06-02 6:45 ` Greg KH [this message]
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=2026060203-protozoan-widow-1b41@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dogestad24@gmail.com \
--cc=hjk@hansjkoch.de \
--cc=jacobsfeder@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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