From: Jean Delvare <khali@linux-fr.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Randy Dunlap <rdunlap@xenotime.net>,
Ben Dooks <ben-linux@fluff.org>,
linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] i2c: remove deprecated callbacks
Date: Thu, 1 Sep 2011 15:01:05 +0200 [thread overview]
Message-ID: <20110901150105.31111b67@endymion.delvare> (raw)
In-Reply-To: <CAM_iQpVGO6Jfcdy4wWN7O-ZpTha2SbfK6xeaf8g9DRGuh=xcbg@mail.gmail.com>
On Thu, 1 Sep 2011 17:12:00 +0800, Américo Wang wrote:
> On Thu, Sep 1, 2011 at 4:52 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > Furthermore, you didn't even check if the deprecated callbacks were
> > still in use. It turns out that there are 9 drivers still using one of
> > them (6 macintosh drivers and 3 sound drivers) so plain removing it
> > will cause build breakages. We obviously don't want to do that, so I am
> > not going to apply your patch (nor mine) for now.
>
> Hmm, sorry that I didn't know this, maybe we can defer the removal
> of these callbacks?
We have to, obviously. And given that this is 50% of the patch, there's
little point in applying the rest now.
> > (...)
> > If you want to help, then instead of sending a patch which I already
> > have and virtually everybody could have written, please get the
> > remaining 3 drivers converted to the current i2c binding model:
> > sound/ppc/keywest.c
> > sound/aoa/codecs/onyx.c
> > sound/aoa/codecs/tas.c
>
> Sure, if I can... so how do we convert them? Any examples?
If it was trivial, someone would have done it already... I converted
most drivers a couple years ago, but the remaining ones only run on
systems I don't have and converting them properly would take intimate
knowledge of the systems in question and preferably actual hardware for
testing.
You can read the possible replacements for the current deprecated
implementations:
Documentation/i2c/instantiating-devices
At the moment I am essentially waiting to see when Ben is headed, as
hopefully the sound drivers can follow the same path. If you want to
help Ben with code review or testing (if you can) this would be great.
--
Jean Delvare
next prev parent reply other threads:[~2011-09-01 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 4:40 [PATCH] i2c: remove deprecated callbacks WANG Cong
2011-09-01 8:52 ` Jean Delvare
2011-09-01 9:12 ` Américo Wang
2011-09-01 13:01 ` Jean Delvare [this message]
2011-09-01 23:24 ` Benjamin Herrenschmidt
2011-09-01 23:32 ` Benjamin Herrenschmidt
2011-09-02 6:28 ` Jean Delvare
[not found] ` <20110902082813.310454af-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-09-02 20:15 ` Benjamin Herrenschmidt
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=20110901150105.31111b67@endymion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=benh@kernel.crashing.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).