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: remove_clientdata_to_null-branch
Date: Sat, 3 Apr 2010 20:13:17 +0200 [thread overview]
Message-ID: <20100403201317.1321b414@hyperion.delvare> (raw)
In-Reply-To: <20100403173646.GB2190-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Hi Wolfram,
On Sat, 3 Apr 2010 19:36:46 +0200, Wolfram Sang wrote:
> just wanted to announce that I put up a branch for removing the
> i2c_set_clientdata(..., NULL)-calls, so you can see what the current status is.
> It will be rebased, so don't work on it (why would you? :)).
>
> http://git.pengutronix.de/?p=wsa/linux-2.6.git;a=shortlog;h=refs/heads/remove_clientdata_to_null
>
> The main cleaning patch is a single patch scheduled for 2.6.35 as discuessed.
> I'd like to add another round of review before sending out a patch to this
> list, probably around -rc4. (Altough I still wonder if we shouldn't wait for
> 2.6.35-rc1, then we could also catch the calls sitting now in linux-next).
>
> Jean, have you noticed this one for 2.6.34?
>
> http://article.gmane.org/gmane.linux.drivers.i2c/5784
I've seen it, but it is something for the power subsystem maintainer
(or akpm if there is none) to apply. I did kill drivers/i2c/chips for a
reason.
--
Jean Delvare
next prev parent reply other threads:[~2010-04-03 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 17:36 remove_clientdata_to_null-branch Wolfram Sang
[not found] ` <20100403173646.GB2190-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-04-03 18:13 ` Jean Delvare [this message]
[not found] ` <20100403201317.1321b414-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-04-03 18:22 ` remove_clientdata_to_null-branch Wolfram Sang
[not found] ` <20100403182207.GC2190-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-04-03 18:27 ` remove_clientdata_to_null-branch Jean Delvare
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=20100403201317.1321b414@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.