The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: i2c@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Eliminate references to new_client in i2c documentation
Date: Fri, 11 May 2007 07:32:58 -0600	[thread overview]
Message-ID: <528646bc0705110632p264f7f01g406802e3084fde0@mail.gmail.com> (raw)
In-Reply-To: <20070511100139.7bf65825@hyperion.delvare>

On 5/11/07, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Grant,
>
> On Thu, 10 May 2007 15:04:16 -0600, Grant Likely wrote:
> > The use of 'new_client' in i2c device allocation has been refered to as
> > a 'disease'.  Replace all occurances of 'struct i2c_client *new_client'
> > in documentation examples with 'struct i2c_client *client'.
> >
> > Also remove unnecessary zero initializtion of .flags since kzalloc is used.
> >
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
>
> Thanks for your contribution, however I made a similar documentation
> cleanup 3 weeks ago:
>   http://lists.lm-sensors.org/pipermail/i2c/2007-April/001075.html
> It's upstream already.

Heh, apparently I don't keep my edge bleeding enough

g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

      reply	other threads:[~2007-05-11 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 21:04 [PATCH 1/2] Eliminate references to new_client in i2c documentation Grant Likely
2007-05-10 21:06 ` [PATCH 2/2] Add driver for Dallas DS1682 elapsed time recorder Grant Likely
2007-05-11  8:01 ` [PATCH 1/2] Eliminate references to new_client in i2c documentation Jean Delvare
2007-05-11 13:32   ` Grant Likely [this message]

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=528646bc0705110632p264f7f01g406802e3084fde0@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=i2c@lm-sensors.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.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