From: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
To: gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
"Jiri Slaby (SUSE)" <jirislaby@kernel.org>
Subject: [PATCH 0/6] char/mwave: cleanup
Date: Wed, 19 Nov 2025 10:19:43 +0100 [thread overview]
Message-ID: <20251119091949.825958-1-jirislaby@kernel.org> (raw)
Hi,
the driver is in a bad shape -- this is a minimal cleanup, so that it is
more or less readable.
Jiri Slaby (SUSE) (6):
char/mwave: remove dead code
char/mwave: remove MWAVE_FUTZ_WITH_OTHER_DEVICES ifdeffery
char/mwave: remove unneeded fops
char/mwave: remove printk tracing
char/mwave: drop printk wrapper
char/mwave: drop typedefs
drivers/char/mwave/3780i.c | 218 +---------------------
drivers/char/mwave/3780i.h | 12 +-
drivers/char/mwave/Makefile | 6 -
drivers/char/mwave/README | 10 -
drivers/char/mwave/mwavedd.c | 337 ++++------------------------------
drivers/char/mwave/mwavedd.h | 76 +-------
drivers/char/mwave/mwavepub.h | 22 +--
drivers/char/mwave/smapi.c | 244 ++++--------------------
drivers/char/mwave/smapi.h | 6 +-
drivers/char/mwave/tp3780i.c | 209 ++++++---------------
drivers/char/mwave/tp3780i.h | 30 +--
11 files changed, 177 insertions(+), 993 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-19 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:19 Jiri Slaby (SUSE) [this message]
2025-11-19 9:19 ` [PATCH 1/6] char/mwave: remove dead code Jiri Slaby (SUSE)
2025-11-19 9:19 ` [PATCH 2/6] char/mwave: remove MWAVE_FUTZ_WITH_OTHER_DEVICES ifdeffery Jiri Slaby (SUSE)
2025-11-19 9:19 ` [PATCH 3/6] char/mwave: remove unneeded fops Jiri Slaby (SUSE)
2025-11-19 9:19 ` [PATCH 4/6] char/mwave: remove printk tracing Jiri Slaby (SUSE)
2025-11-19 9:19 ` [PATCH 5/6] char/mwave: drop printk wrapper Jiri Slaby (SUSE)
2025-11-19 9:19 ` [PATCH 6/6] char/mwave: drop typedefs Jiri Slaby (SUSE)
2025-11-19 12:54 ` [PATCH 0/6] char/mwave: cleanup Arnd Bergmann
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=20251119091949.825958-1-jirislaby@kernel.org \
--to=jirislaby@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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®