From: Adrian Bunk <bunk@stusta.de>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
linux-joystick@atrey.karlin.mff.cuni.cz
Subject: Re: [2.6 patch] drivers/input/: possible cleanups
Date: Sat, 5 Nov 2005 16:09:59 +0100 [thread overview]
Message-ID: <20051105150959.GG5368@stusta.de> (raw)
In-Reply-To: <20051104131228.GA5208@ucw.cz>
On Fri, Nov 04, 2005 at 02:12:28PM +0100, Vojtech Pavlik wrote:
> On Fri, Nov 04, 2005 at 01:57:42PM +0100, Adrian Bunk wrote:
>
> > On Fri, Nov 04, 2005 at 01:42:07PM +0100, Vojtech Pavlik wrote:
> > > On Fri, Nov 04, 2005 at 01:35:41PM +0100, Adrian Bunk wrote:
> > > > This patch contains the following possible cleanups:
> > > > - make needlessly glbal code static
> > >
> > > Agreed.
> > >
> > > > - gameport/gameport: #if 0 the unused global function gameport_reconnect
> > >
> > > That one should be an EXPORT_SYMBOL() API. If the export is missing,
> > > then that's the bug that needs to be fixed.
> > >...
> >
> > There isn't even a header providing a function prototype which is quite
> > strange for a part of an API.
>
> It's a planned API (a mirror of what the serio abstraction does), the
> drivers don't use it yet.
Can you either apply my patch to #if 0 it, or (if usage is planned very
soon) add a function prototype to a header file?
In both cases, we get rid of a warning both by sparse and with the gcc
-Wmissing-prototypes flag.
> Vojtech Pavlik
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-11-05 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 12:35 [2.6 patch] drivers/input/: possible cleanups Adrian Bunk
2005-11-04 12:42 ` Vojtech Pavlik
2005-11-04 12:57 ` Adrian Bunk
2005-11-04 13:12 ` Vojtech Pavlik
2005-11-05 15:09 ` Adrian Bunk [this message]
2005-11-05 20:20 ` Vojtech Pavlik
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=20051105150959.GG5368@stusta.de \
--to=bunk@stusta.de \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-joystick@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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