linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: Tjernlund <tjernlund@tjernlund.se>,
	linuxppc-dev@ozlabs.org, Jean Delvare <khali@linux-fr.org>,
	i2c@lm-sensors.org
Subject: Re: [RFC] Rework of i2c-mpc.c - Freescale i2c driver
Date: Mon, 5 Nov 2007 19:41:39 -0500	[thread overview]
Message-ID: <9e4733910711051641m5ff0e651ke9a43daa51fd14b@mail.gmail.com> (raw)
In-Reply-To: <472F8267.8070106@freescale.com>

On 11/5/07, Scott Wood <scottwood@freescale.com> wrote:
> >>> One side effect is that legacy style i2c drivers won't work anymore.
> >> If you mean legacy-style client drivers, why not?
> >
> > i2c_new_device() doesn't work with legacy-style client drivers.
>
> No, but they should still work the old way.

I'm not in favor trying to support both legacy and new style i2c
drivers.  It took me all of five minutes to convert an existing legacy
driver to the new style. Pretty much all you need to do is delete code
(about 100 lines). So I'd recommend converting the drivers we are
interest in instead of trying to support both types.

-- 
Jon Smirl
jonsmirl@gmail.com

  parent reply	other threads:[~2007-11-06  0:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 15:14 [RFC] Rework of i2c-mpc.c - Freescale i2c driver Jon Smirl
2007-11-05 19:22 ` Matt Sealey
2007-11-05 19:51   ` Jon Smirl
2007-11-05 19:55     ` Scott Wood
2007-11-05 20:04       ` Jon Smirl
2007-11-05 20:06         ` Scott Wood
2007-11-05 20:11   ` Grant Likely
2007-11-05 19:43 ` Scott Wood
2007-11-05 20:30   ` Jon Smirl
2007-11-05 20:51     ` Scott Wood
2007-11-05 21:52       ` Matt Sealey
2007-11-05 21:55         ` Scott Wood
2007-11-05 23:03           ` Grant Likely
2007-11-06 17:32         ` Jean Delvare
2007-11-06 18:53           ` Matt Sealey
2007-11-06 20:31             ` Jean Delvare
2007-11-06 21:06               ` Matt Sealey
2007-11-05 22:46       ` Grant Likely
2007-11-06  0:33         ` Jon Smirl
2007-11-06 22:20         ` David Gibson
2007-11-06  0:41       ` Jon Smirl [this message]
2007-11-06 17:02         ` Scott Wood
2007-11-06  4:25       ` Jon Smirl
2007-11-06  4:40         ` Stephen Rothwell
2007-11-06 19:02           ` Jon Smirl
2007-11-06 22:22             ` David Gibson
2007-11-06 17:29       ` Jean Delvare
2007-11-06 17:36         ` Scott Wood
2007-11-06 18:10           ` Jean Delvare
2007-11-06 18:26             ` Grant Likely
2007-11-06 18:26               ` Grant Likely
2007-11-06 19:34               ` Jean Delvare
2007-11-06 18:29             ` Scott Wood
2007-11-06 17:45         ` Jon Smirl
2007-11-06 18:17           ` Jean Delvare
2007-11-06 19:07             ` Jon Smirl
2007-11-06  1:34   ` Jon Smirl
2007-11-06  2:28     ` Stephen Rothwell
2007-11-05 20:03 ` Grant Likely
2007-11-05 20:41 ` Jon Smirl

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=9e4733910711051641m5ff0e651ke9a43daa51fd14b@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=i2c@lm-sensors.org \
    --cc=khali@linux-fr.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=tjernlund@tjernlund.se \
    /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;
as well as URLs for NNTP newsgroup(s).