From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-i2c@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-can@vger.kernel.org
Subject: Re: randconfig build error with next-20141001, in drivers/i2c/algos/i2c-algo-bit.c
Date: Tue, 07 Oct 2014 14:37:30 +0200 [thread overview]
Message-ID: <5433DE8A.6030603@peak-system.com> (raw)
In-Reply-To: <5433AB31.9090603@hartkopp.net>
Le 07/10/2014 10:58, Oliver Hartkopp a écrit :
> On 10/06/2014 08:09 PM, Randy Dunlap wrote:
>> On 10/06/14 10:39, Oliver Hartkopp wrote:
>>> AFAICS there is 'just' a style problem as 'configs should not enable entire
>>> subsystems'. But it finally is a correct and valid Kconfig, right?
>> Yes, right.
> (..)
>
>> In the unlikely case that I2C is not enabled, the user should have to enable
>> it instead of a solitary driver enabling it. IOW, if a subsystem is disabled,
>> the user probably wanted it that way and a single driver should not override
>> that setting.
> Due to the fact that a change to 'depends on I2C' would make the config option
> invisible (and therefore not selectable) in the case I2C was (unlikely)
> disabled I would finally vote to leave it as-is.
>
> The current Kconfig entry already contains a description that points to the
> requirement to have I2C and I2C_ALGOBIT to be enabled to compile this driver:
>
> config CAN_PEAK_PCIEC
> bool "PEAK PCAN-ExpressCard Cards"
> depends on CAN_PEAK_PCI
> select I2C
> select I2C_ALGOBIT
> default y
> ---help---
> Say Y here if you want to use a PCAN-ExpressCard from PEAK-System
> Technik. This will also automatically select I2C and I2C_ALGO
> configuration options.
>
> AFAIK the PEAK PCAN-ExpressCard is usually used in x86 architecture Laptops,
> so it's near to an academic discussion as x86 usually selects I2C ;-)
>
> @Stephane: When updating the help text to introduce the PCAN-ExpressCard 34
> support anyway you might probably add some more information *why* the I2C
> support is needed (for CAN transceiver settings and status LED).
>
> And /s/I2C_ALGO/I2C_ALGOBIT/ :-)
Ok! (FYI, I had already prepared the help text for introducing the
PCIEC34. I will subst I2C_ALGO as well. I'll prepare the patch asap...)
Regards,
Stéphane
> Tnx & best regards,
> Oliver
--
PEAK-System Technik GmbH
Sitz der Gesellschaft Darmstadt
Handelsregister Darmstadt HRB 9183
Geschaeftsfuehrung: Alexander Gach, Uwe Wilhelm
--
next prev parent reply other threads:[~2014-10-07 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:37 randconfig build error with next-20141001, in drivers/i2c/algos/i2c-algo-bit.c Jim Davis
2014-10-01 23:26 ` Randy Dunlap
2014-10-02 15:18 ` Fwd: " Oliver Hartkopp
2014-10-06 7:52 ` Stephane Grosjean
2014-10-06 8:09 ` Oliver Hartkopp
2014-10-06 8:42 ` Stephane Grosjean
2014-10-06 8:06 ` Oliver Hartkopp
2014-10-06 16:52 ` Randy Dunlap
2014-10-06 17:39 ` Oliver Hartkopp
2014-10-06 18:09 ` Randy Dunlap
2014-10-07 8:58 ` Oliver Hartkopp
2014-10-07 12:37 ` Stephane Grosjean [this message]
[not found] ` <5433AB31.9090603-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2014-10-07 17:03 ` Randy Dunlap
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=5433DE8A.6030603@peak-system.com \
--to=s.grosjean@peak-system.com \
--cc=jim.epost@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=socketcan@hartkopp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.