From: Greg KH <gregkh@suse.de>
To: "figo.zhang" <figo1802@126.com>
Cc: Ben Nizette <bn@niasdigital.com>,
hjanssen <hjanssen@microsoft.com>,
haiyangz <haiyangz@microsoft.com>,
torvalds <torvalds@linux-foundation.org>, akpm <akpm@osdl.org>,
mingo <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re: [staging/hv] why it not follow kernel codingstyle?
Date: Fri, 15 Jan 2010 07:04:04 -0800 [thread overview]
Message-ID: <20100115150404.GA9813@suse.de> (raw)
In-Reply-To: <1293729.429011263564253037.JavaMail.coremail@bj126app34.126.com>
On Fri, Jan 15, 2010 at 10:04:13PM +0800, figo.zhang wrote:
>
> Now it has made the Codingstyle rule, anyone should follow it , right?
Patches are always gladly accepted to fix this stuff up.
thanks,
greg k-h
prev parent reply other threads:[~2010-01-15 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 6:29 [staging/hv] why it not follow kernel codingstyle? Figo.zhang
2010-01-12 7:08 ` 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 [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=20100115150404.GA9813@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=bn@niasdigital.com \
--cc=figo1802@126.com \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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