From: Dmitry Torokhov <dtor@insightbb.com>
To: lm-sensors@lm-sensors.org
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>,
Krzysztof Helt <krzysztof.h1@wp.pl>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] Hardware monitoring subsystem maintainer positionis open
Date: Sat, 14 Apr 2007 22:07:15 -0400 [thread overview]
Message-ID: <200704142207.16800.dtor@insightbb.com> (raw)
In-Reply-To: <461DDF7D.1060101@hhs.nl>
Hi,
On Thursday 12 April 2007 03:27, Hans de Goede wrote:
> Krzysztof Helt wrote:
>
> >> * Must follow kernel coding style guidelines
> >
> > Is there any tool to check this? If there is one, a basic
> > instruction how to use it would be great.
> >
>
> No tool.
Passing new drivres through scripts/Lindent and analyzing the
dirrerences can highlight differences between kernel style and
author's (note that I do not advocate mechanically passing
everything though Lindent).
--
Dmitry
next prev parent reply other threads:[~2007-04-15 2:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070410150227.1bac05b5@hyperion.delvare>
2007-04-10 13:56 ` [lm-sensors] Hardware monitoring subsystem maintainer position is open David Hubbard
2007-04-10 15:40 ` Hans de Goede
2007-04-10 15:46 ` David Hubbard
2007-04-10 22:22 ` Rudolf Marek
2007-04-10 23:02 ` David Hubbard
2007-04-11 9:24 ` Hans de Goede
2007-04-11 15:08 ` Juerg Haefliger
[not found] ` <461dca480d7ec@wp.pl>
2007-04-12 7:27 ` [lm-sensors] Hardware monitoring subsystem maintainer positionis open Hans de Goede
2007-04-15 2:07 ` Dmitry Torokhov [this message]
2007-04-11 9:49 ` Hardware monitoring subsystem maintainer position is open Jean Delvare
2007-04-11 10:06 ` [lm-sensors] " David Hubbard
2007-04-11 14:49 ` Gene Heskett
2007-04-15 15:03 ` [lm-sensors] " Mark M. Hoffman
2007-04-15 17:54 ` Juerg Haefliger
2007-04-15 18:16 ` Rudolf Marek
2007-04-17 8:45 ` 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=200704142207.16800.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=j.w.r.degoede@hhs.nl \
--cc=krzysztof.h1@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.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