linux-kernel - Re: [PATCH] staging: iio: adt7316: replace sprintf() with sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHp75VejBvRX=5psgVgGPCsKk7gVgcDUd1q3Gn+4_jyzk=2pEw@mail.gmail.com>
Date: Tue, 18 Nov 2025 14:10:25 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Nuno Sá <noname.nuno@...il.com>
Cc: Jonathan Cameron <jic23@...nel.org>, Shi Hao <i.shihao.999@...il.com>, 
	Michael.Hennerich@...log.com, lars@...afoo.de, dlechner@...libre.com, 
	nuno.sa@...log.com, andy@...nel.org, gregkh@...uxfoundation.org, 
	linux-iio@...r.kernel.org, linux-staging@...ts.linux.dev, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: iio: adt7316: replace sprintf() with sysfs_emit()

On Tue, Nov 18, 2025 at 10:17 AM Nuno Sá <noname.nuno@...il.com> wrote:
> On Sun, 2025-11-16 at 15:28 +0000, Jonathan Cameron wrote:
> > On Sun, 16 Nov 2025 13:08:07 +0200
> > Andy Shevchenko <andy.shevchenko@...il.com> wrote:

...

> > Applied, but I will note that this driver is a long way from suitable
> > for moving out of staging and I would be surprised if more than
> > one or two of the lines changed in this patch make it through the
> > necessary refactors (should anyone actually have another go at
> > doing them).  Anyhow, I still think this is worth taking just to
> > reduce the noise of remaining instances of this.
> >
> > I'd have deleted this long ago except I actually have one somewhere
> > and it one of the supported parts was still listed as suitable for
> > new designs when I checked not long ago.
>
> Seems to be now "just" in production. So no longer advised for new designs. I gave a
> quick look and this is far from being a simple driver. It would require a fair amount
> of work to bring it out of staging. So, are there users relying on staging drivers?

If there is no choice, yes. For example FBTFT is famous for being used
by IoT / DIY _a lot_. Currently a bit less since we got tinyDRM
subsystem with most popular drivers reimplemented there.

> But I would assume that for staging we are still free to drop support it?

At any level, we are still free to drop :-) Just different conditions
applied. For staging is basically an "effective immediately" case.

-- 
With Best Regards,
Andy Shevchenko