From: Dan Carpenter <dan.carpenter@oracle•com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail•com>
Cc: "pebolle@tiscali•nl" <pebolle@tiscali•nl>,
"gregkh@linuxfoundation•org" <gregkh@linuxfoundation•org>,
"jasowang@redhat•com" <jasowang@redhat•com>,
"driverdev-devel@linuxdriverproject•org"
<driverdev-devel@linuxdriverproject•org>,
"olaf@aepfle•de" <olaf@aepfle•de>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"stephen@networkplumber•org" <stephen@networkplumber•org>,
"stefanha@redhat•com" <stefanha@redhat•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"apw@canonical•com" <apw@canonical•com>,
"davem@davemloft•net" <davem@davemloft•net>
Subject: Re: [PATCH V3 3/7] Drivers: hv: vmbus: add APIs to send/recv hvsock packet and get the r/w-ability
Date: Fri, 24 Jul 2015 11:33:47 +0300 [thread overview]
Message-ID: <20150724083347.GV5371@mwanda> (raw)
In-Reply-To: <20150724062701.GA5525@sudip-PC>
On Fri, Jul 24, 2015 at 11:57:01AM +0530, Sudip Mukherjee wrote:
> This is also ok, the function is supposed to return ret or-ed with the
> relevant flags based on the scan position. It is considered error if 0
> is returned (without any flag).
Yeah. You're right. I looked through my list again this morning and
they all seem fine...
regards,
dan carpenter
prev parent reply other threads:[~2015-07-24 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 10:58 [PATCH V3 3/7] Drivers: hv: vmbus: add APIs to send/recv hvsock packet and get the r/w-ability Dexuan Cui
2015-07-21 14:07 ` Vitaly Kuznetsov
2015-07-22 10:09 ` Dexuan Cui
2015-07-22 10:35 ` Dan Carpenter
2015-07-23 3:05 ` Dexuan Cui
2015-07-23 10:10 ` Dan Carpenter
2015-07-23 10:24 ` Dan Carpenter
2015-07-23 11:05 ` Dexuan Cui
2015-07-24 6:27 ` Sudip Mukherjee
2015-07-24 8:33 ` Dan Carpenter [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=20150724083347.GV5371@mwanda \
--to=dan.carpenter@oracle$(echo .)com \
--cc=apw@canonical$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=driverdev-devel@linuxdriverproject$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jasowang@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olaf@aepfle$(echo .)de \
--cc=pebolle@tiscali$(echo .)nl \
--cc=stefanha@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=sudipm.mukherjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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