All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	"D. Kelly" <user.kernel@gmail.com>,
	"mailing list: linux-kernel" <linux-kernel@vger.kernel.org>,
	Linux I2C <i2c@lm-sensors.org>
Subject: Re: Problem with restricted I2C algorithms in kernel 2.6.26!
Date: Thu, 7 Aug 2008 23:06:52 +0200	[thread overview]
Message-ID: <20080807230652.20f231e4@hyperion.delvare> (raw)
In-Reply-To: <37219a840808071203y36775d8fx5cccd653da04e1fc@mail.gmail.com>

Hi Michael,

On Thu, 7 Aug 2008 15:03:36 -0400, Michael Krufky wrote:
> I agree with Trent and D.Kelly
> 
> These options should be made available to the user -- We should go
> with the patch that Jean posted, "Subject: i2c: Let users select
> algorithm drivers manually again" -- this is a fair compromise for
> both sides -- users that dont know should leave the automatic
> selection enabled.  Users that know better can disable the automatic
> selection and enable what they need.
> 
> The statement, "just have the external driver merged into the kernel"
> is not a solution.

Why not, please? A vast majority of drivers work fine that way today. I
am still waiting for someone to give me a good reason why some other
drivers supposedly can't be merged upstream (something better than
"believe me, it's impossible".)

> Removing the option to build those additional algos is a regression, IMHO

Will be addressed soon, do not worry.

-- 
Jean Delvare

  reply	other threads:[~2008-08-07 21:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 19:33 Problem with restricted I2C algorithms in kernel 2.6.26! D. Kelly
2008-07-26  6:59 ` Andrew Morton
2008-07-26 14:34   ` [i2c] " Jon Smirl
     [not found] ` <5ab239b10807161233i6c1c4d0we01ea1b8e6ccaa5b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-07 11:13   ` Jean Delvare
2008-08-07 11:13     ` Jean Delvare
     [not found]     ` <20080807131357.59399ddf-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-07 16:01       ` Trent Piepho
2008-08-07 16:01         ` [i2c] " Trent Piepho
2008-08-07 16:14         ` Jean Delvare
     [not found]           ` <20080807181416.5de4ce6d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-07 17:19             ` Jean Delvare
2008-08-07 17:19               ` Jean Delvare
     [not found]               ` <20080807191943.72d1802d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-07 17:29                 ` Randy Dunlap
2008-08-07 17:29                   ` Randy Dunlap
2008-08-07 23:41           ` Trent Piepho
2008-08-08  9:37             ` Jean Delvare
2008-08-08 17:52               ` Trent Piepho
2008-08-10 11:07                 ` Adrian Bunk
2008-08-07 18:39     ` Sam Ravnborg
2008-08-07 18:49       ` Jean Delvare
2008-08-07 19:03         ` Michael Krufky
2008-08-07 21:06           ` Jean Delvare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-07 21:34 mkrufky
     [not found] ` <489B6A66.40605-dJidKbW2IEtAfugRpC6u6w@public.gmane.org>
2008-08-08  0:17   ` Stefan Richter
2008-08-08  0:17     ` Stefan Richter
2008-08-08  9:28 ` 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=20080807230652.20f231e4@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@linuxtv.org \
    --cc=sam@ravnborg.org \
    --cc=user.kernel@gmail.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 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.