From: "Arnd Bergmann" <arnd@arndb.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"old king" <fy15309206903@gmail.com>
Cc: ralphs@netwinder.org, linux-kernel@vger.kernel.org
Subject: Re: nwbutton: lost wakeup in button_read() -- worth fixing, or is this driver done?
Date: Sat, 22 Aug 2026 19:58:54 +0200 [thread overview]
Message-ID: <035d9d92-691a-4e01-96e3-a4ffe60a4f53@app.fastmail.com> (raw)
In-Reply-To: <2026082255-arrogance-flanking-bd89@gregkh>
On Sat, Aug 22, 2026, at 18:08, Greg KH wrote:
> On Sat, Aug 22, 2026 at 06:06:13PM +0200, Greg KH wrote:
>
> I don't think it can even build, given that there is no definition for
> machine_is_netwinder() anywhere in the tree that I can see. So maybe
> many of these drivers can just be removed now. Arnd, any ideas?
The machine_is_netwinder() function is autogenerated from
arch/arm/tools/mach-types, I would assume that the driver
still works as well as it ever has.
However, I have marked most arm32 board files including
this one as deprecated this merge window, and expect that
we can remove the platform and all associated drivers
for 7.4 or 7.5.
Please keep the driver for now, until we are sure the
platform removal goes ahead. I have already written
a patch to remove it, and plan to send it once the platform
removal is queued in the soc tree. I'll also take
care of nwflash, ds1620, mxc-rnga, and bh1770glc.
No need to fix any bugs in the driver though.
Arnd
next prev parent reply other threads:[~2026-08-22 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 16:01 nwbutton: lost wakeup in button_read() -- worth fixing, or is this driver done? old king
2026-08-22 16:06 ` Greg KH
2026-08-22 16:08 ` Greg KH
2026-08-22 17:58 ` Arnd Bergmann [this message]
2026-08-23 0:12 ` old king
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=035d9d92-691a-4e01-96e3-a4ffe60a4f53@app.fastmail.com \
--to=arnd@arndb.de \
--cc=fy15309206903@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralphs@netwinder.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