From: Greg KH <gregkh@suse.de>
To: wwang <wei_wang@realsil.com.cn>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rts_pstor: fix sparse warning
Date: Wed, 16 Feb 2011 07:49:55 -0800 [thread overview]
Message-ID: <20110216154955.GC29006@suse.de> (raw)
In-Reply-To: <4D5B3419.7010909@realsil.com.cn>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Feb 16, 2011 at 10:19:05AM +0800, wwang wrote:
> Dear Greg:
>
> Do you mean that exactly one modification corresponds to one patch? Such
> as, if I add 2 static modifier and delete one function, I should send 3
> patches?
No, the way you redid them was just fine.
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-16 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 1:43 [PATCH] staging: rts_pstor: fix sparse warning wei_wang
2011-02-16 2:09 ` Greg KH
2011-02-16 2:19 ` wwang
2011-02-16 15:49 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-15 1:15 wei_wang
2011-02-15 12:21 ` Greg KH
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=20110216154955.GC29006@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wei_wang@realsil.com.cn \
/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