From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [patch 2.6.25-rc1] i2c: kerneldoc for most i/o calls
Date: Sat, 17 May 2008 18:14:03 +0200 [thread overview]
Message-ID: <20080517181403.44089575@hyperion.delvare> (raw)
In-Reply-To: <200805170733.36937.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
On Sat, 17 May 2008 07:33:36 -0700, David Brownell wrote:
> On Saturday 17 May 2008, Jean Delvare wrote:
> > I'd rather spell it "16-bit", that's what developers are used to I
> > think.
>
> ISTR some "how 2 right gud inglish" style guide, maybe the
> Univerity of Chicago one (or Turabian, or Strunk and White),
> saying to use the word form, not the digit form, except when
> the text is really about numbers/dates. Certainly *mixing*
> two forms would be bad, and having only one digit-format
> number is a degenerate case of mixing. (Ergo my scribble.)
Apparently the kernel developers don't give a damn to whatever style
guide you read. "16 bit" overrules "sixteen bit" by 2858 to 3 in the
current kernel tree ;)
> > Please send an updated patch, or if you prefer I can adjust it myself.
>
> It'll go faster if you make these last changes ...
Done.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-05-17 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 0:51 [patch 2.6.25-rc1] i2c: kerneldoc for most i/o calls David Brownell
[not found] ` <200805031751.26920.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-05-17 12:20 ` Jean Delvare
[not found] ` <20080517142011.1493e584-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-05-17 14:33 ` David Brownell
[not found] ` <200805170733.36937.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-05-17 16:14 ` Jean Delvare [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=20080517181403.44089575@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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