From: Randy Dunlap <randy.dunlap@oracle.com>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH -mmotm] tty.h: make function static
Date: Thu, 14 Jan 2010 08:18:19 -0800 [thread overview]
Message-ID: <20100114081819.e9ff37a0.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201001132042.o0DKgaSR027272@imap1.linux-foundation.org>
From: Randy Dunlap <randy.dunlap@oracle.com>
I get a few dozen of these warnings when using
gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2):
In file included from mmotm-2010-0113-1217/init/do_mounts.c:5:
mmotm-2010-0113-1217/include/linux/tty.h: In function 'tty_port_get':
mmotm-2010-0113-1217/include/linux/tty.h:469: warning: '______f' is static but declared in inline function 'tty_port_get' which is not static
so make the function static inline.
(may be needed in mainline also; or a gcc problem?)
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
include/linux/tty.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- mmotm-2010-0113-1217.orig/include/linux/tty.h
+++ mmotm-2010-0113-1217/include/linux/tty.h
@@ -464,7 +464,7 @@ extern int tty_port_alloc_xmit_buf(struc
extern void tty_port_free_xmit_buf(struct tty_port *port);
extern void tty_port_put(struct tty_port *port);
-extern inline struct tty_port *tty_port_get(struct tty_port *port)
+static inline struct tty_port *tty_port_get(struct tty_port *port)
{
if (port)
kref_get(&port->kref);
---
~Randy
next prev parent reply other threads:[~2010-01-14 16:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 20:17 mmotm 2010-01-13-12-17 uploaded akpm
2010-01-13 22:16 ` mmotm 2010-01-13-12-17 - 'make oldconfig' dies Valdis.Kletnieks
2010-01-14 16:07 ` mmotm 2010-01-13-12-17 uploaded (cgroup) Randy Dunlap
2010-01-14 17:20 ` Ben Blum
2010-01-18 2:03 ` Randy Dunlap
2010-01-14 16:18 ` Randy Dunlap [this message]
2010-01-15 19:33 ` mmotm 2010-01-13-12-17 uploaded Jiri Slaby
2010-01-15 23:38 ` oops in uevent_helper [was: mmotm 2010-01-13-12-17 uploaded] Jiri Slaby
2010-01-22 23:52 ` Andrew Morton
2010-02-10 19:54 ` Jiri Slaby
2010-02-11 20:57 ` Andi Kleen
2010-02-11 22:25 ` Andrew Morton
2010-02-12 2:39 ` Neil Horman
2010-02-12 3:10 ` Andrew Morton
2010-02-12 5:21 ` Andi Kleen
2010-02-12 5:27 ` Andrew Morton
2010-02-12 17:06 ` Neil Horman
2010-02-14 17:32 ` Jiri Slaby
2010-02-14 17:54 ` Neil Horman
2010-02-15 20:12 ` Paul E. McKenney
2010-02-15 21:42 ` Neil Horman
2010-02-15 22:16 ` Paul E. McKenney
2010-02-16 1:37 ` Neil Horman
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=20100114081819.e9ff37a0.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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
Powered by JetHome