From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: kernel@pengutronix.de, John Ogness <john.ogness@linutronix.de>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
linux-serial@vger.kernel.org,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/3] tty: Convert to platform remove callback returning void
Date: Sun, 18 Feb 2024 09:53:53 +0100 [thread overview]
Message-ID: <cover.1708246007.git.u.kleine-koenig@pengutronix.de> (raw)
Hello,
this series converts all remaining (three) drivers below drivers/tty to
struct platform_driver::remove_new(). See commit 5c5a7680e67b
("platform: Provide a remove callback that returns no value") for an
extended explanation and the eventual goal.
Two conversations are trivial, because their .remove() callbacks
returned zero unconditionally. The pmac_zilog serial driver had an error
path in its remove callback that however was never taken and so could be
dropped.
There are no interdependencies between these patches, so they could be
picked up individually. However I'd expect them to go in all together
via Greg's tree.
Uwe Kleine-König (3):
tty: amiserial: Convert to platform remove callback returning void
tty: goldfish: Convert to platform remove callback returning void
serial: pmac_zilog: Convert to platform remove callback returning void
drivers/tty/amiserial.c | 6 ++----
drivers/tty/goldfish.c | 5 ++---
drivers/tty/serial/pmac_zilog.c | 9 ++-------
3 files changed, 6 insertions(+), 14 deletions(-)
base-commit: d37e1e4c52bc60578969f391fb81f947c3e83118
--
2.43.0
next reply other threads:[~2024-02-18 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 8:53 Uwe Kleine-König [this message]
2024-02-18 8:53 ` [PATCH 3/3] serial: pmac_zilog: Convert to platform remove callback returning void Uwe Kleine-König
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=cover.1708246007.git.u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=aneesh.kumar@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).