All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: removing set_clientdata(NULL)
Date: Mon, 29 Mar 2010 16:49:10 +0100	[thread overview]
Message-ID: <20100329154910.GE13239@sirena.org.uk> (raw)
In-Reply-To: <20100329172734.7cd7341d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

On Mon, Mar 29, 2010 at 05:27:34PM +0200, Jean Delvare wrote:
> On Mon, 29 Mar 2010 17:09:56 +0200, Wolfram Sang wrote:

> > - shall this better go via the i2c-tree?

> This seems simpler, yes. I don't think subsystem or driver maintainers
> need to be bothered with what is really only a cleanup.

What about those subsystems where the maintainers applied the patch from
the first round (adding the explicit set to NULL where it had been
missing)?

  parent reply	other threads:[~2010-03-29 15:49 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
     [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 [this message]
     [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=20100329154910.GE13239@sirena.org.uk \
    --to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
    --cc=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.