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 v5 03/14] nubus: Use static functions where possible
Date: Sat, 13 Jan 2018 17:37:13 -0500 (EST) [thread overview]
Message-ID: <d7e94b9834f0e5e3981295dc836484fbc598bd2c.1515814167.git.fthain@telegraphics.com.au> (raw)
In-Reply-To: <cover.1515814167.git.fthain@telegraphics.com.au>
This fixes a couple of warnings from 'make W=1':
drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot'
drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus'
Tested-by: Stan Johnson <userm57@yahoo.com>
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
---
drivers/nubus/nubus.c | 4 ++--
include/linux/nubus.h | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/nubus/nubus.c b/drivers/nubus/nubus.c
index b6c97e07f15e..35056cee94b1 100644
--- a/drivers/nubus/nubus.c
+++ b/drivers/nubus/nubus.c
@@ -793,7 +793,7 @@ static struct nubus_board * __init nubus_add_board(int slot, int bytelanes)
return board;
}
-void __init nubus_probe_slot(int slot)
+static void __init nubus_probe_slot(int slot)
{
unsigned char dp;
unsigned char *rp;
@@ -827,7 +827,7 @@ void __init nubus_probe_slot(int slot)
}
}
-void __init nubus_scan_bus(void)
+static void __init nubus_scan_bus(void)
{
int slot;
diff --git a/include/linux/nubus.h b/include/linux/nubus.h
index 55b9a4569a69..e525669f1991 100644
--- a/include/linux/nubus.h
+++ b/include/linux/nubus.h
@@ -92,7 +92,6 @@ extern struct nubus_dev* nubus_devices;
extern struct nubus_board* nubus_boards;
/* Generic NuBus interface functions, modelled after the PCI interface */
-void nubus_scan_bus(void);
#ifdef CONFIG_PROC_FS
extern void nubus_proc_init(void);
#else
--
2.13.6
next prev parent reply other threads:[~2018-01-13 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 22:37 [PATCH v5 00/14] Modernization and fixes for NuBus subsystem Finn Thain
2018-01-13 22:37 ` [PATCH v5 07/14] nubus: Remove redundant code Finn Thain
2018-01-13 22:37 ` [PATCH v5 10/14] nubus: Rework /proc/bus/nubus/s/ implementation Finn Thain
2018-01-13 22:37 ` [PATCH v5 04/14] nubus: Fix log spam Finn Thain
2018-01-13 22:37 ` [PATCH v5 09/14] nubus: Generalize block resource handling Finn Thain
2018-01-13 22:37 ` [PATCH v5 13/14] nubus: Add expansion_type values for various Mac models Finn Thain
2018-01-13 22:37 ` [PATCH v5 05/14] nubus: Validate slot resource IDs Finn Thain
2018-01-13 22:37 ` Finn Thain [this message]
2018-01-13 22:37 ` [PATCH v5 11/14] nubus: Rename struct nubus_dev Finn Thain
2018-01-13 22:37 ` [PATCH v5 01/14] nubus: Avoid array underflow and overflow Finn Thain
2018-01-13 22:37 ` [PATCH v5 08/14] nubus: Clean up whitespace Finn Thain
2018-01-13 22:37 ` [PATCH v5 02/14] nubus: Fix up header split Finn Thain
2018-01-13 22:37 ` [PATCH v5 06/14] nubus: Call proc_mkdir() not more than once per slot directory Finn Thain
2018-01-13 22:37 ` [PATCH v5 12/14] nubus: Adopt standard linked list implementation Finn Thain
2018-01-13 22:37 ` [PATCH v5 14/14] nubus: Add support for the driver model Finn Thain
2018-01-16 18:10 ` [PATCH v5 00/14] Modernization and fixes for NuBus subsystem 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=d7e94b9834f0e5e3981295dc836484fbc598bd2c.1515814167.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).