All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "sochin.jiang" <sochin@aliyun.com>, berrange@redhat.com
Cc: qemu-devel@nongnu.org, sochin.jiang@huawei.com,
	QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] channel-file: fix wrong parameter comments
Date: Sun, 23 Apr 2017 12:15:02 +0300	[thread overview]
Message-ID: <03e2cdb8-0c47-71e8-92f8-f6b6dce3581e@msgid.tls.msk.ru> (raw)
In-Reply-To: <1490365705-2912-1-git-send-email-sochin@aliyun.com>

24.03.2017 17:28, sochin.jiang wrote:
> From: "sochin.jiang" <sochin@aliyun.com>
> 
>     fix wrong parameter comments in channel-file.h.

Applied to -trivial.  Please don't duplicate subject and commit comment,
it's enough to leave commit empty if everything is said in the subject :)

Thanks,

/mjt

      parent reply	other threads:[~2017-04-23  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 14:28 [Qemu-devel] [PATCH] channel-file: fix wrong parameter comments sochin.jiang
2017-03-24 15:47 ` Marc-André Lureau
2017-04-23  9:15 ` Michael Tokarev [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=03e2cdb8-0c47-71e8-92f8-f6b6dce3581e@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sochin.jiang@huawei.com \
    --cc=sochin@aliyun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.