From: "Figo.zhang" <figo1802@126.com>
To: gregkh@suse.de, hjanssen@microsoft.com, haiyangz@microsoft.com,
torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [staging/hv] why it not follow kernel codingstyle?
Date: Tue, 12 Jan 2010 14:29:30 +0800 [thread overview]
Message-ID: <4B4C16CA.4010401@126.com> (raw)
hi all,
i read the driver/staging/hv code, why it will apply into kernel tree
that it not fellow the kernel codingstyle?
it ruin the kernel tree, it had better let the author rewrite it fellow
the "linux kernel CodingStyle".
see Documentation/CodingStyle.
Best,
Figo.zhang
next reply other threads:[~2010-01-12 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 6:29 Figo.zhang [this message]
2010-01-12 7:08 ` [staging/hv] why it not follow kernel codingstyle? Figo.zhang
2010-01-12 8:10 ` Ben Nizette
[not found] ` <1293729.429011263564253037.JavaMail.coremail@bj126app34.126.com>
2010-01-15 15:04 ` Greg KH
[not found] <4650630.501001263607923679.JavaMail.coremail@bj126app13.126.com>
2010-01-16 2:32 ` Figo.zhang
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=4B4C16CA.4010401@126.com \
--to=figo1802@126.com \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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