public inbox for linux-i2c@vger.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 0/6] i2c: Get rid of the legacy binding model
Date: Sun, 3 May 2009 09:05:53 +0200	[thread overview]
Message-ID: <20090503090553.0351ddfd@hyperion.delvare> (raw)
In-Reply-To: <200905021214.02937.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

On Sat, 2 May 2009 12:14:02 -0700, David Brownell wrote:
> On Saturday 02 May 2009, Jean Delvare wrote:
> >  Documentation/feature-removal-schedule.txt |   10 -
> >  Documentation/i2c/writing-clients          |   16 -
> >  drivers/i2c/i2c-core.c                     |  366 +++--------------------------
> >  include/linux/i2c.h                        |   57 +----
> 
> Which makes all but patch #4 *very* easy to review.
> All they do is remove code.  Unless that breaks a
> build, those removals have a hard time making any
> trouble.  ;)

Well, removing code can always break things. For example, say I remove
all the locking code in the kernel... ;)

> >  4 files changed, 48 insertions(+), 401 deletions(-)
> > 
> > From a binary perspective, "size" announces an 18% shrink.
> 
> And Linux now builds without all those warnings, yes?

Yes it does :)

> Plus from a code complexity perspective, it's even
> better ... it removes 100% of the high level confusion
> associated with that legacy model, and the bugs and
> fragility caused by that.  (Or maybe I should say
> that it *finishes* removing that.)

Thanks for doing all the hard work :)

> Glad to see this.  I presume this will sit in -next
> for a while and merge in 2.6.31-early?

Exactly. Where "early" is unfortunately bound to the few remaining
legacy drivers, the conversion of which is supposed to be merged by
their respective maintainers. But anyway, the hard deadline is
2.6.31-rc1.

-- 
Jean Delvare

      parent reply	other threads:[~2009-05-03  7:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02  9:38 [PATCH 0/6] i2c: Get rid of the legacy binding model Jean Delvare
     [not found] ` <20090502113856.39940f1e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-05-02  9:39   ` [PATCH 1/6] i2c: Kill client_register and client_unregister methods Jean Delvare
2009-05-02  9:40   ` [PATCH 2/6] i2c: Get rid of the legacy binding model Jean Delvare
     [not found]     ` <20090502114020.41c38247-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-05-02 19:03       ` David Brownell
     [not found]         ` <200905021203.43974.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-05-03  7:25           ` Jean Delvare
2009-05-02  9:41   ` [PATCH 3/6] i2c: Drop i2c_probe function Jean Delvare
2009-05-02  9:42   ` [PATCH 4/6] i2c: Merge i2c_attach_client into i2c_new_device Jean Delvare
2009-05-02  9:43   ` [PATCH 5/6] i2c: Kill is_newstyle_driver Jean Delvare
2009-05-02  9:45   ` [PATCH 6/6] i2c: Kill the redundant client list Jean Delvare
2009-05-02 18:16   ` [PATCH 0/6] i2c: Get rid of the legacy binding model David Brownell
2009-05-02 19:14   ` David Brownell
     [not found]     ` <200905021214.02937.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-05-03  7:05       ` Jean Delvare [this message]

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=20090503090553.0351ddfd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox