From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Theuns Verwoerd <theuns@bluewatersys.com>
Cc: r.marek@sh.cvut.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] I2C: AD7414 I2C chip driver for Linux-2.6.17.7
Date: Thu, 3 Aug 2006 20:23:36 -0700 [thread overview]
Message-ID: <20060803202336.07c2b2a2.rdunlap@xenotime.net> (raw)
In-Reply-To: <44D28C60.1000304@bluewatersys.com>
On Fri, 04 Aug 2006 11:53:04 +1200 Theuns Verwoerd wrote:
> AD7414 Temperature Sensor I2C driver. I2C chip driver for the Analog
> Devices AD7414 device, exposes raw and decoded registers via sysfs.
> Signed-off-by: Theuns Verwoerd <theuns.verwoerd@bluewatersys.com>
> ---
> Tested on a custom EP9315-based board developed in-house. Fairly trivial
> driver; really just exposes the raw registers and temperature reading
> to userspace.
> Patch is relative to stock Linux-2.6.17.7
Patches should be made against latest mainline kernel, e.g.,
2.6.18-rc3 (unless they are specifically for an -mm patch),
although it probably doesn't matter in this case.
> [This is my first go at a kernel submission, so feel free to point out
> anything
> that should be done differently]
> ---
> diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
> linux-2.6.17.7-vanilla/drivers/i2c/chips/ad7414.c
> linux-2.6.17.7/drivers/i2c/chips/ad7414.c
> --- linux-2.6.17.7-vanilla/drivers/i2c/chips/ad7414.c 1970-01-01
> 12:00:00.000000000 +1200
> +++ linux-2.6.17.7/drivers/i2c/chips/ad7414.c 2006-08-04
> 10:28:37.000000000 +1200
1/ Thunderbird is breaking (splitting) your lines for you. :(
See if http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
helps any. Try sending a patch to yourself and test if you
can apply it. Or use a different mail client/app.
Those 7 lines above should be 3 lines.
You may need to unset some "flowed" attribute in tbird
(I'm not sure of its full, correct name.)
2/ Either thunderbird is converting tabs to spaces or the
driver source does not contain tabs -- just lots of spaces.
Please indent struct fields with one tab, embedded struct fields
with 2 tabs, etc.
3/ Macro continuation lines should be indented.
4/ sysfs files should contain only one value per file. Use
multiple files for multiple values.
5/ Code labels should not be indented or maybe indented one space,
and certainly not indented more than the following source lines.
6/ device_create_file() and friends can return errors. They need
to be checked for success/fail.
7/ Header files should be included in linux/ alpha order, then
asm/ alpha order, then local.h files unless there are reasons
that this order won't work.
(Yes, only linux/ applies here.)
---
~Randy
next prev parent reply other threads:[~2006-08-04 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 23:53 Theuns Verwoerd
2006-08-04 3:23 ` Randy.Dunlap [this message]
2006-08-06 11:31 ` Jean Delvare
2006-08-08 4:38 ` Theuns Verwoerd
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=20060803202336.07c2b2a2.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=r.marek@sh.cvut.cz \
--cc=theuns@bluewatersys.com \
/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
all inboxes | Powered by JetHome®