From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 00/14] Modernization and fixes for NuBus subsystem
Date: Sat, 11 Nov 2017 01:12:48 -0500 (EST) [thread overview]
Message-ID: <cover.1510377368.git.fthain@telegraphics.com.au> (raw)
This series begins with cleanups and fixes for the NuBus subsystem and
finishes with a patch to add support for the Linux Driver Model.
The next series, which requires this one, will modernize NuBus drivers.
Finn Thain (14):
nubus: Avoid array underflow and overflow
nubus: Fix up header split
nubus: Use static functions where possible
nubus: Fix log spam
nubus: Validate slot resource IDs
nubus: Call proc_mkdir() not more than once per slot
nubus: Remove redundant code
nubus: Clean up whitespace
nubus: Don't needlessly unpack vidname and driver resources
nubus: Depopulate /proc/bus/nubus/s/
nubus: Repopulate /proc/bus/nubus/s/
nubus: Rename struct nubus_dev
nubus: Add expansion_type values for various Mac models
nubus: Add support for the driver model
arch/m68k/include/asm/macintosh.h | 9 +-
arch/m68k/mac/config.c | 110 +++----
drivers/net/ethernet/8390/mac8390.c | 12 +-
drivers/net/ethernet/natsemi/macsonic.c | 12 +-
drivers/nubus/Makefile | 2 +-
drivers/nubus/bus.c | 87 ++++++
drivers/nubus/nubus.c | 500 ++++++++++++++++++--------------
drivers/nubus/proc.c | 247 ++++++++++------
drivers/video/fbdev/macfb.c | 2 +-
include/linux/nubus.h | 200 ++++++++-----
include/uapi/linux/nubus.h | 23 --
11 files changed, 724 insertions(+), 480 deletions(-)
create mode 100644 drivers/nubus/bus.c
--
2.13.6
next reply other threads:[~2017-11-11 6:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 6:12 Finn Thain [this message]
2017-11-11 6:12 ` [PATCH 10/14] nubus: Depopulate /proc/bus/nubus/s/ Finn Thain
2017-11-11 6:12 ` [PATCH 04/14] nubus: Fix log spam Finn Thain
2017-11-11 15:04 ` Joe Perches
2017-11-11 23:47 ` Finn Thain
2017-11-12 0:08 ` Joe Perches
2017-11-11 6:12 ` [PATCH 05/14] nubus: Validate slot resource IDs Finn Thain
2017-11-11 6:12 ` [PATCH 02/14] nubus: Fix up header split Finn Thain
2017-11-11 6:12 ` [PATCH 09/14] nubus: Don't needlessly unpack vidname and driver resources Finn Thain
2017-11-11 6:12 ` [PATCH 11/14] nubus: Repopulate /proc/bus/nubus/s/ Finn Thain
2017-11-13 8:56 ` Geert Uytterhoeven
2017-11-14 0:21 ` Finn Thain
2017-11-11 6:12 ` [PATCH 03/14] nubus: Use static functions where possible Finn Thain
2017-11-11 6:12 ` [PATCH 01/14] nubus: Avoid array underflow and overflow Finn Thain
2017-11-11 6:12 ` [PATCH 08/14] nubus: Clean up whitespace Finn Thain
2017-11-11 6:12 ` [PATCH 06/14] nubus: Call proc_mkdir() not more than once per slot Finn Thain
2017-11-11 6:12 ` [PATCH 07/14] nubus: Remove redundant code Finn Thain
2017-11-11 6:12 ` [PATCH 13/14] nubus: Add expansion_type values for various Mac models Finn Thain
2017-11-11 6:12 ` [PATCH 14/14] nubus: Add support for the driver model Finn Thain
2017-11-11 8:45 ` Greg Kroah-Hartman
2017-11-11 8:46 ` Greg Kroah-Hartman
2017-11-12 3:52 ` Finn Thain
2017-11-11 6:12 ` [PATCH 12/14] nubus: Rename struct nubus_dev Finn Thain
2017-11-13 8:57 ` Geert Uytterhoeven
2017-11-14 0:18 ` Finn Thain
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.1510377368.git.fthain@telegraphics.com.au \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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;
as well as URLs for NNTP newsgroup(s).