From: Dan Carpenter <error27@gmail.com>
To: Grewstad <dogestad24@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
Jacob Feder <jacobsfeder@gmail.com>
Subject: Re: [PATCH] staging: axis-fifo: remove driver
Date: Tue, 2 Jun 2026 16:11:59 +0300 [thread overview]
Message-ID: <ah7Wn3-meqmDLk_d@stanley.mountain> (raw)
In-Reply-To: <CAD03fjZQwgvDbBdh6A=1FeGVn4Na29ww2DzG3anuk2sOd0-4EA@mail.gmail.com>
On Tue, Jun 02, 2026 at 06:31:27PM +0530, Grewstad wrote:
> On Tue, Jun 2, 2026 at 5:07 PM Dan Carpenter <error27@gmail.com> wrote:
> >
> > On Tue, Jun 02, 2026 at 04:01:53PM +0530, Arihan Bhor wrote:
> >
> > I don't think we should delete this driver. From reading the git
> > log, Ovidiu Panait was obviously using this code last year. Let's
> > also add Jacob Feder, although he hasn't touched the code in 8 years,
> > he still might know if there are other users.
>
> I could not find any user-space applications that depend on this driver.
>
> https://lore.kernel.org/lkml/CAD03fjb=_kW9=q9YV4qnQ5GD=HMB5Bx7pf3+AFcgDR2gVc1V6Q@mail.gmail.com/
> I was looking for any users of this driver on the linux-kernel, linux-staging,
> and linux-arm-kernel mailing lists as well as Jacob Feder, and received no
> replies since I posted it 1 day ago. If someone is using it or maintaining a
> proprietary app, they will complain and we can bring the driver back.
Here are people using it and running into issues in Jan 2025.
https://adaptivesupport.amd.com/s/question/0D54U00008zRBdISAW/vitis-is-not-creating-a-driver-entry-for-axififomm-43?language=zh_CN
Someone provides a work around:
https://adaptivesupport.amd.com/s/question/0D54U00008sLBuMSAW/how-to-use-the-axi-stream-fifo-drivers-xllfifoh-xllfifogc-etc-in-the-project?language=en_US
Then Ovidiu Panait fixed the bug in Sep by adding the correct
compatible.
regards,
dan carpenter
next prev parent reply other threads:[~2026-06-02 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:31 [PATCH] staging: axis-fifo: remove driver Arihan Bhor
2026-06-02 11:37 ` Dan Carpenter
2026-06-02 13:01 ` Grewstad
2026-06-02 13:11 ` Dan Carpenter [this message]
2026-06-02 21:26 ` Ovidiu Panait
2026-06-03 3:18 ` Grewstad
2026-06-03 3:20 ` Grewstad
2026-06-03 12:25 ` Grewstad
2026-06-03 13:25 ` Michal Simek
-- strict thread matches above, loose matches on Subject: below --
2026-06-03 13:47 Denny Lin
2026-06-04 9:52 ` Grewstad
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=ah7Wn3-meqmDLk_d@stanley.mountain \
--to=error27@gmail.com \
--cc=dogestad24@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacobsfeder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.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