From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Greg KH <greg@kroah.com>
Cc: Jean Delvare <khali@linux-fr.org>,
LKML <linux-kernel@vger.kernel.org>,
video4linux-list@redhat.com
Subject: Re: [PATCH 2.6] I2C: Drop I2C_DEVNAME and i2c_clientname
Date: Thu, 01 Sep 2005 00:14:27 -0300 [thread overview]
Message-ID: <1125544467.16937.3.camel@localhost> (raw)
In-Reply-To: <20050831205604.GJ19361@kroah.com>
Em Qua, 2005-08-31 às 13:56 -0700, Greg KH escreveu:
> On Wed, Aug 31, 2005 at 12:34:58PM -0300, Mauro Carvalho Chehab wrote:
> > Em Ter, 2005-08-30 ?s 23:20 +0200, Jean Delvare escreveu:
> > > Hi Mauro,
> > >
> > > > (...) it would be nice not to have a different I2C
> > > > API for every single 2.6 version :-) It would be nice to change I2C
> > > > API once and keep it stable for a while.
> >
> > > The Linux 2.6 development model is designed around a relatively fast
> > > move from -mm to Linus' tree, which implies incremental changes all the
> > > time. I'm only doing that.
> > It is ok to change code, but, IMHO, API should be more stable.
>
> I take it you have not read Documentation/stable_api_nonsense.txt yet?
No I din't :-)
> If not, please do, it shows that what you are asking for will not
> happen.
I was not asking for a 'stable' one.. but a less variant... anyway, I
can survive with this policy ;-)
>
> good luck,
>
> greg k-h
>
Cheers,
Mauro.
prev parent reply other threads:[~2005-09-01 3:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 17:57 [PATCH 2.6] I2C: Drop I2C_DEVNAME and i2c_clientname Jean Delvare
2005-08-22 20:09 ` Mauro Carvalho Chehab
2005-08-24 22:19 ` Jean Delvare
2005-08-30 0:12 ` Mauro Carvalho Chehab
2005-08-30 19:44 ` Greg KH
2005-08-30 21:20 ` Jean Delvare
2005-08-31 15:34 ` Mauro Carvalho Chehab
2005-08-31 20:56 ` Greg KH
2005-09-01 3:14 ` Mauro Carvalho Chehab [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=1125544467.16937.3.camel@localhost \
--to=mchehab@brturbo.com.br \
--cc=greg@kroah.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox