public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Adam Turk <bofh1234@hotmail.com>
Cc: linux-kernel@vger.kernel.org, i2c@lm-sensors.org
Subject: Re: I2C_PARPORT_LIGHT dependence problem
Date: Sun, 20 Jan 2008 11:11:51 +0100	[thread overview]
Message-ID: <20080120111151.08b0266a@hyperion.delvare> (raw)
In-Reply-To: <BAY101-W29C4113A3B79204F64B0DCC8430@phx.gbl>

Hi Adam,

On Sat, 19 Jan 2008 13:37:05 -0500, Adam Turk wrote:
> I am updating an old config to run on 2.6.23.14 and noticed I am
> still prompted for I2C_PARPORT_LIGHT even though I don't have
> the parallel port driver enabled.  Shouldn't I2C_PARPORT_LIGHT
> depend on the parallel port being selected? (...)
> 
> Symbol: I2C_PARPORT_LIGHT [=n]
>   │ Prompt: Parallel port adapter (light)
>   │   Defined at drivers/i2c/busses/Kconfig:348
>   │   Depends on: I2C
>   │   Location:
>   │     -> Device Drivers
>   │       -> I2C support (I2C [=m])
>   │         -> I2C Hardware Bus support
>   │   Selects: I2C_ALGOBIT

The help text says:

"This driver is a light version of i2c-parport.  It doesn't depend on
the parport driver, and uses direct I/O access instead."

So I think that the (lack of) dependencies is correct. We don't want to
force the user to select PARPORT (and built the parport driver) to get
access to the i2c-parport-light driver which does NOT need this parport
driver.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2008-01-20 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 18:37 I2C_PARPORT_LIGHT dependence problem Adam Turk
2008-01-20 10:11 ` Jean Delvare [this message]
     [not found]   ` <20080120111151.08b0266a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-01-21  2:12     ` Adam Turk

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=20080120111151.08b0266a@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=bofh1234@hotmail.com \
    --cc=i2c@lm-sensors.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