From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-m68k@lists.linux-m68k.org
Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 0/5] zorro: Miscellaneous cleanups
Date: Sun, 12 Jan 2020 17:49:44 +0100 [thread overview]
Message-ID: <20200112164949.20196-1-geert@linux-m68k.org> (raw)
Hi all,
This patch series contains miscellaneous cleanups for the Zorro bus
code.
Geert Uytterhoeven (5):
zorro: Make zorro_match_device() static
zorro: Fix zorro_bus_match() kerneldoc
zorro: Use zorro_match_device() helper in zorro_bus_match()
zorro: Remove unused zorro_dev_driver()
zorro: Move zorro_bus_type to bus-private header file
drivers/zorro/zorro-driver.c | 16 +++++-----------
drivers/zorro/zorro.h | 7 +++++++
include/linux/zorro.h | 12 ------------
3 files changed, 12 insertions(+), 23 deletions(-)
--
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2020-01-12 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 16:49 Geert Uytterhoeven [this message]
2020-01-12 16:49 ` [PATCH 1/5] zorro: Make zorro_match_device() static Geert Uytterhoeven
2020-01-12 16:49 ` [PATCH 2/5] zorro: Fix zorro_bus_match() kerneldoc Geert Uytterhoeven
2020-01-12 16:49 ` [PATCH 3/5] zorro: Use zorro_match_device() helper in zorro_bus_match() Geert Uytterhoeven
2020-01-12 16:49 ` [PATCH 4/5] zorro: Remove unused zorro_dev_driver() Geert Uytterhoeven
2020-01-12 16:49 ` [PATCH 5/5] zorro: Move zorro_bus_type to bus-private header file Geert Uytterhoeven
2020-02-10 11:16 ` [PATCH 0/5] zorro: Miscellaneous cleanups Geert Uytterhoeven
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=20200112164949.20196-1-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).