From: Lee Jones <lee@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
kernel.org@treblig.org, arnd@arndb.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: pcf50633-input - Remove
Date: Wed, 2 Jul 2025 15:55:03 +0100 [thread overview]
Message-ID: <20250702145503.GR10134@google.com> (raw)
In-Reply-To: <6utlzamf6luhexdvtpjbqnlkrdh5bj6gcoj2h7ql7kjxyjo2zt@csylxspamkch>
On Tue, 01 Jul 2025, Dmitry Torokhov wrote:
> On Tue, Jul 01, 2025 at 02:58:06PM +0000, Dr. David Alan Gilbert wrote:
> > Lee:
> >
> > * Dmitry Torokhov (dmitry.torokhov@gmail.com) wrote:
> > > On Sun, Jun 29, 2025 at 10:28:20PM +0100, linux@treblig.org wrote:
> > > > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> > > >
> > > > The pcf50633 was used as part of the OpenMoko devices but
> > > > the support for its main chip was recently removed in:
> > > > commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
> > > >
> > > > Remove the input code.
> > > >
> > > > This was originally posted as a set of pcf50633 removals in March,
> > > > and is the only major component that hasn't been picked up.
> > > > https://lore.kernel.org/all/20250311014959.743322-1-linux@treblig.org/
> > > >
> > > > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> > >
> > > Applied, thank you.
> >
> > I see Dmitry has got that into -next, so I've posted a patch to take
> > out the pcf50633 header which is the last bit left.
>
> Lee, do you want me to take it through my tree as well to avoid juggling
> inter-tree dependencies?
If the driver is unused, it shouldn't cause too many issues. Let's
ensure that all of these get applied for this cycle and all should be
well.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-07-02 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 21:28 linux
2025-06-30 5:05 ` Dmitry Torokhov
2025-06-30 11:10 ` Dr. David Alan Gilbert
2025-07-01 14:58 ` Dr. David Alan Gilbert
2025-07-01 18:10 ` Dmitry Torokhov
2025-07-02 14:55 ` Lee Jones [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=20250702145503.GR10134@google.com \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel.org@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.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
all inboxes | Powered by JetHome®