From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
Rudy Zhang <rudy.zhangmin@huawei.com>,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com
Cc: xen-devel@lists.xenproject.org, wu.wubin@huawei.com,
boby.chen@huawei.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen-scsiback: some modifications about code comment
Date: Thu, 19 Feb 2015 14:16:33 +0000 [thread overview]
Message-ID: <54E5F041.2000705@citrix.com> (raw)
In-Reply-To: <54D85CE5.2040404@suse.com>
On 09/02/15 07:08, Juergen Gross wrote:
> On 02/07/2015 04:31 AM, Rudy Zhang wrote:
>> From: Tao Chen <boby.chen@huawei.com>
>>
>> Signed-off-by: Tao Chen <boby.chen@huawei.com>
>
> Are some white space fixes in comments really worth a patch?
No.
David
prev parent reply other threads:[~2015-02-19 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 3:31 [PATCH] xen-scsiback: some modifications about code comment Rudy Zhang
2015-02-09 7:08 ` Juergen Gross
2015-02-19 14:16 ` David Vrabel [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=54E5F041.2000705@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boby.chen@huawei.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rudy.zhangmin@huawei.com \
--cc=wu.wubin@huawei.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).