public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>,
	Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: [-mm patch] drivers/pci/hotplug/acpiphp_glue.c: make a function static
Date: Sun, 9 Apr 2006 16:50:47 +0200	[thread overview]
Message-ID: <20060409145047.GC8454@stusta.de> (raw)
In-Reply-To: <20060408031405.5e5131da.akpm@osdl.org>

On Sat, Apr 08, 2006 at 03:14:05AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.17-rc1-mm1:
>...
> +gregkh-pci-acpiphp-configure-_prt-v3.patch
>...
>  PCI tree updates
>...

This patch makes the needlessly global acpiphp_bus_trim() static.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.17-rc1-mm2-full/drivers/pci/hotplug/acpiphp_glue.c.old	2006-04-09 16:13:00.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/drivers/pci/hotplug/acpiphp_glue.c	2006-04-09 16:13:13.000000000 +0200
@@ -928,7 +928,7 @@
  * @handle: handle to acpi namespace
  *
  */
-int acpiphp_bus_trim(acpi_handle handle)
+static int acpiphp_bus_trim(acpi_handle handle)
 {
 	struct acpi_device *device;
 	int retval;


  parent reply	other threads:[~2006-04-09 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 10:14 2.6.17-rc1-mm2 Andrew Morton
2006-04-09 11:31 ` [-mm patch] drivers/w1/w1.c: fix a compile error Adrian Bunk
2006-04-09 11:39   ` Evgeniy Polyakov
2006-04-09 14:50 ` Adrian Bunk [this message]
2006-04-10  0:27   ` [-mm patch] drivers/pci/hotplug/acpiphp_glue.c: make a function static MUNEDA Takahiro
2006-04-09 14:58 ` [-mm patch] drivers/char/drm/drm_memory.c: possible cleanups Adrian Bunk
2006-04-11 12:08 ` [PATCH] x86_64 sparsemem does not need node_mem_map Andy Whitcroft

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=20060409145047.GC8454@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=muneda.takahiro@jp.fujitsu.com \
    /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