From: David Miller <davem@davemloft.net>
To: vaibhavmurkute88@gmail.com
Cc: stefanha@redhat.com, mst@redhat.com, jasowang@redhat.com,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: vhost: vsock: fixed a brace coding style issue
Date: Fri, 09 Mar 2018 11:39:59 -0500 (EST) [thread overview]
Message-ID: <20180309.113959.2082976207958220439.davem@davemloft.net> (raw)
In-Reply-To: <20180309025603.4890-1-vaibhavmurkute88@gmail.com>
From: Vaibhav Murkute <vaibhavmurkute88@gmail.com>
Date: Fri, 9 Mar 2018 08:26:03 +0530
> Fixed a coding style issue.
>
> Signed-off-by: Vaibhav Murkute <vaibhavmurkute88@gmail.com>
Applied to net-next, thanks.
prev parent reply other threads:[~2018-03-09 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 2:56 [PATCH] drivers: vhost: vsock: fixed a brace coding style issue Vaibhav Murkute
2018-03-09 9:52 ` Stefan Hajnoczi
2018-03-09 16:39 ` David Miller [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=20180309.113959.2082976207958220439.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=vaibhavmurkute88@gmail.com \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).