Linux I2C development
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: legacy drivers in staging?
Date: Sun, 1 Mar 2009 11:36:41 +0100	[thread overview]
Message-ID: <20090301113641.33a462d2@hyperion.delvare> (raw)
In-Reply-To: <20090301101306.GB23093-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Hi Wolfram,

On Sun, 1 Mar 2009 11:13:06 +0100, Wolfram Sang wrote:
> when having another look at the status page of legacy drivers in the i2c-wiki,
> I stumbled over the drivers from 'staging'. Do they really need to appear
> there? I hope the removal of the legacy binding will not depend on those
> drivers ;)

I am not sure myself. I agree we don't want to delay the removal of the
legacy binding just because of these drivers. But OTOH I see little
point in having a staging directory [1] if drivers being placed there
break as soon as there is a core kernel change. I guess we are supposed
to update these drivers as we do for all other drivers.

So, ideally, someone would convert these drivers so that they do not
break when legacy drivers are removed. My hope was that the author of
these drivers would do it when seeing the warnings which i2c.h spits
out. But if this doesn't happen, someone else will have to take care.
That being said I think that there is much more work needed on these
drivers, on the V4L side.

Bottom line is that, is these drivers are the last ones blocking the
removal of the legacy i2c driver, I will either attempt to convert them
the quick-and-dirty way, or I will mark them as broken and leave it to
somebody else to fix them. They will not delay us.

[1] To be honest I was not really fond of the idea of a staging drivers
directory in the first place anyway.

-- 
Jean Delvare

  parent reply	other threads:[~2009-03-01 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 10:13 legacy drivers in staging? Wolfram Sang
     [not found] ` <20090301101306.GB23093-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-03-01 10:36   ` Jean Delvare [this message]
     [not found]     ` <20090301113641.33a462d2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-01 19:26       ` Wolfram Sang

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=20090301113641.33a462d2@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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