From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: removing set_clientdata(NULL)
Date: Mon, 29 Mar 2010 17:09:56 +0200 [thread overview]
Message-ID: <20100329150956.GB6717@pengutronix.de> (raw)
In-Reply-To: <20100329162812.548d131b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
Hi Jean,
> Sorry for being a little quiet, I took a long, well-deserved week-end
> off and didn't have the time to reply before I left. Now I'm back...
No worries, no rush :)
> Yes, my intent was to add a call to i2c_set_clientdata(x, NULL) in
> i2c_device_remove(). We would do this immediately, so that drivers can
> start removing the call on their end quickly (and new ones are not
> added.)
>
> Can you please send the patch for i2c-core and Documentation/i2c? It's
> not difficult but I don't want to steal your credits.
Yes, can do this in a few hours (already midnight here), this is for 2.6.34
then.
> It would also be fair to warn all the developers you already contacted
> with your first attempt and let them know that it is being cancelled,
> and let them know the new plan. Hopefully this will avoid useless
> commits.
Can do this, too. About the removal of the i2c_set_clientdata-calls:
- shall I prepare a series for that, too?
- also for 2.6.34?
- also patches per subsystem?
- shall this better go via the i2c-tree?
> > I could check if there is any probe-function calling get_clientdata and making
> > use of that? That is probably the most obvious thing which would need to rely
> > on the current behaviour or did I miss something?
>
> You are right, but I really hope you won't catch anybody doing this.
> This would go against the device driver model.
I'd also be surprised if that would find something.
Regards,
Wolfram
PS: I will also have a look at the pca-issue after that.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-03-29 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 12:15 removing set_clientdata(NULL) Wolfram Sang
[not found] ` <20100327121558.GA5880-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-03-29 14:28 ` Jean Delvare
[not found] ` <20100329162812.548d131b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-03-29 15:09 ` Wolfram Sang [this message]
[not found] ` <20100329150956.GB6717-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-03-29 15:27 ` Jean Delvare
[not found] ` <20100329172734.7cd7341d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-03-29 15:49 ` Mark Brown
[not found] ` <20100329154910.GE13239-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2010-03-29 16:43 ` Jean Delvare
2010-03-30 2:48 ` Wolfram Sang
[not found] ` <20100330024831.GB23862-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-03-30 7:05 ` 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=20100329150956.GB6717@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).