From: Andrew Morton <akpm@linux-foundation.org>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: platform-driver-x86@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Richard Purdie <rpurdie@rpsys.net>,
Andres Salomon <dilinger@queued.net>,
Ed Wildgoose <kernel@wildgooses.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3 1/1] alix2: supplement driver to include GPIO button support
Date: Wed, 25 Jan 2012 15:16:22 -0800 [thread overview]
Message-ID: <20120125151622.6621f6ce.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F208A70.1050709@redfish-solutions.com>
On Wed, 25 Jan 2012 16:04:16 -0700
Philip Prindeville <philipp@redfish-solutions.com> wrote:
> > This is odd. There are no references to this from outside this file
> > and it's hard to see how a wireless driver could use this - any such
> > driver would have to load this module on *all* machines (even non-x86)
> > simply to resolve this symbol.
>
> It's for an out-of-tree driver that's only ever built for Alix hardware.
This should have been changelogged! And a code comment would be good,
too - if it confused me now, it will confused others later. And such a
code comment will help prevent others from coming in and "cleaning up"
the code later on.
Out-of-tree drivers are unpopular. Where is this driver, what is its
license and what are the prospects of making it in-tree?
I don't personally have problems with helping out-of-tree drivers but
making it EXPORT_SYMBOL_GPL() would set minds at rest.
> Since it's only 4 bytes and one exported symbol, I figured it was acceptable...
>
> I can remove it, resubmit, and use a patch locally in my tree if that's preferable
What we should do depends on the above issues...
next prev parent reply other threads:[~2012-01-25 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 19:56 [PATCH v3 1/1] alix2: supplement driver to include GPIO button support Philip Prindeville
2012-01-23 22:56 ` Andres Salomon
2012-01-25 22:57 ` Andrew Morton
2012-01-25 23:04 ` Philip Prindeville
2012-01-25 23:16 ` Andrew Morton [this message]
2012-01-25 23:47 ` Philip Prindeville
2012-01-26 1:08 ` Andrew Morton
2012-01-26 1:37 ` Philip Prindeville
2012-01-26 10:15 ` Ed Wildgoose
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=20120125151622.6621f6ce.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=dilinger@queued.net \
--cc=dwmw2@infradead.org \
--cc=kernel@wildgooses.com \
--cc=philipp@redfish-solutions.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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