From: Eric Andersson <eric.andersson@unixphere.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc/bmp085: Enable building as a module
Date: Wed, 26 Jun 2013 13:08:23 +0200 [thread overview]
Message-ID: <20130626110823.GA25070@scully.xfiles.lan> (raw)
In-Reply-To: <1372162617.4006.0.camel@deadeye.wl.decadent.org.uk>
On 13:16 Tue 25 Jun , Ben Hutchings wrote:
> On Tue, 2013-06-25 at 09:27 +0200, Eric Andersson wrote:
> > On 15:10 Mon 24 Jun , Ben Hutchings wrote:
> > > Commit 985087dbcb02 'misc: add support for bmp18x chips to the bmp085
> > > driver' changed the BMP085 config symbol to a boolean. I see no
> > > reason why the shared code cannot be built as a module, so change it
> > > back to tristate.
> > >
> > > Cc: Eric Andersson <eric.andersson@unixphere.com>
> > > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > > ---
> > > drivers/misc/Kconfig | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> > > index c002d86..7a68184 100644
> > > --- a/drivers/misc/Kconfig
> > > +++ b/drivers/misc/Kconfig
> > > @@ -451,7 +451,7 @@ config ARM_CHARLCD
> > > still useful.
> > >
> > > config BMP085
> > > - bool
> > > + tristate
> > > depends on SYSFS
> > >
> > > config BMP085_I2C
> > >
> >
> > There is no reason for building the common code stand-alone. The BMP085
> > config option is only selectable via the BMP085_I2C/_SPI options.
>
> Yes, but it is then always built-in.
Good point. This change is fine by me.
--
Best regards,
Eric
http://www.unixphere.com
prev parent reply other threads:[~2013-06-26 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:10 Ben Hutchings
2013-06-25 7:27 ` Eric Andersson
2013-06-25 12:16 ` Ben Hutchings
2013-06-26 11:08 ` Eric Andersson [this message]
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=20130626110823.GA25070@scully.xfiles.lan \
--to=eric.andersson@unixphere.com \
--cc=arnd@arndb.de \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®