All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: Linux-I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch 2.6.28-rc5] i2c:  remove i2c_adapter.clist_lock
Date: Tue, 25 Nov 2008 12:01:00 +0100	[thread overview]
Message-ID: <20081125120100.6581f394@hyperion.delvare> (raw)
In-Reply-To: <200811250224.01610.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

On Tue, 25 Nov 2008 02:24:01 -0800, David Brownell wrote:
> On Tuesday 25 November 2008, Jean Delvare wrote:
> > I'm not sure I want to take this change at this point. Call me chicken,
> > but I seem to recall problems with legacy i2c clients last time we
> > tried to clean up this area.
> 
> I did test this with the legacy "eeprom" and "i2c-stub" as you had
> suggested.  Worked fine ... this is different from previous passes,
> as it removes the lock instead of the list, and doesn't attempt to
> change how the list is (mis/ab)used.

Which kernel version? Since 2.6.27, the eeprom driver is no longer a
legacy driver. Instead it's a new-style driver with the
optional .detect() callback.

This is why I am reluctant to change this now: there aren't too many
legacy drivers left, so testing their code paths isn't easy, and if
anything isn't correct we might not notice it until it hits the users.

> But if you prefer to wait until the list can go too, OK.

Yes, please.

-- 
Jean Delvare

  parent reply	other threads:[~2008-11-25 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 22:38 [patch 2.6.28-rc5] i2c: remove i2c_adapter.clist_lock David Brownell
     [not found] ` <200811201438.08788.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-25  9:12   ` Jean Delvare
     [not found]     ` <20081125101203.58e3f032-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-11-25 10:24       ` David Brownell
     [not found]         ` <200811250224.01610.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-25 11:01           ` Jean Delvare [this message]
     [not found]             ` <20081125120100.6581f394-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-11-25 11:27               ` David Brownell
     [not found]                 ` <200811250327.08464.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-25 11:54                   ` 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=20081125120100.6581f394@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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.