From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Christian Gmeiner
<christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH] Fix Kconfig for I2C-Algos
Date: Mon, 16 Jun 2008 20:15:45 +0200 [thread overview]
Message-ID: <20080616201545.7e514d36@hyperion.delvare> (raw)
In-Reply-To: <3192d3cd0806161024u6a07abddpe4af78b3bb6ec4e7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Christian,
On Mon, 16 Jun 2008 17:24:59 +0000, Christian Gmeiner wrote:
> this patch fixes wrong kconf file so that it will be possible to
> select wanted i2c algorithms.
We moved in the exact opposite direction two months ago, on the basis
that i2c bus drivers select the algorithm driver they need
automatically so the user shouldn't have to care:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3845de25c5f83cd52729570f7b501679d37ca8de
So, it's not a bug, it's a feature. If you have some i2c bus driver
which needs an i2c algorithm driver and doesn't select it, fix that
driver.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-06-16 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:24 [PATCH] Fix Kconfig for I2C-Algos Christian Gmeiner
[not found] ` <3192d3cd0806161024u6a07abddpe4af78b3bb6ec4e7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-16 18:15 ` Jean Delvare [this message]
[not found] ` <3192d3cd0806162300j2b8e93a4h3d3c17919d0d562@mail.gmail.com>
[not found] ` <3192d3cd0806162300j2b8e93a4h3d3c17919d0d562-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-17 6:01 ` Christian Gmeiner
[not found] ` <3192d3cd0806162301r1acdc66eo7f0676b17db8ddee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-17 6:36 ` Jean Delvare
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=20080616201545.7e514d36@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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