From: Roman Zippel <zippel@linux-m68k.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: questions about config files, I2C and hardware sensors (2.5.59)
Date: Sat, 18 Jan 2003 02:40:41 +0100 [thread overview]
Message-ID: <3E28B099.4E85C56D@linux-m68k.org> (raw)
In-Reply-To: Pine.LNX.4.44.0301170636120.13098-100000@dell
Hi,
"Robert P. J. Day" wrote:
> so the issues:
>
> 1) trivial: comment is wrong, there is no dependency on
> EXPERIMENTAL
This has to be answered by the I2C maintainer.
> 2) since, in the sourcing Kconfig file, I2C_PROC *already* depends
> on I2C, is there any practical value in having the dependency
> "I2C && I2C_PROC". wouldn't "depends on I2C_PROC" be sufficient?
Yes.
> 3) finally, given that the comment at the top is adamant that
> all of these options depend on I2C and I2C_PROC, wouldn't it
> be cleaner to just make the menu itself say:
>
> menu "I2C HW Sensors Mainboard Support"
> depends on I2C && I2C_PROC (or just I2C_PROC)
> ...
>
> and let the internal options inherit this dependency?
Yes, the menu entry needs the dependencies as well.
bye, Roman
next prev parent reply other threads:[~2003-01-18 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 11:53 questions about config files, I2C and hardware sensors (2.5.59) Robert P. J. Day
2003-01-18 1:40 ` Roman Zippel [this message]
2003-01-18 11:40 ` Robert P. J. Day
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=3E28B099.4E85C56D@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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