From: Joe Perches <joe@perches.com>
To: KY Srinivasan <kys@microsoft.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>, Robo Bot <apw@canonical.com>,
Jason Wang <jasowang@redhat.com>,
"eli@mellanox.com" <eli@mellanox.com>,
"jackm@mellanox.com" <jackm@mellanox.com>,
"yevgenyp@mellanox.com" <yevgenyp@mellanox.com>,
John Ronciak <john.ronciak@intel.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next V2 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V)
Date: Mon, 18 Apr 2016 10:00:19 -0700 [thread overview]
Message-ID: <1460998819.1917.10.camel@perches.com> (raw)
In-Reply-To: <BL2PR03MB19081E9C9AAB13E6F608D08FA06B0@BL2PR03MB1908.namprd03.prod.outlook.com>
On Mon, 2016-04-18 at 16:52 +0000, KY Srinivasan wrote:
[]
> > > +bool ixgbevf_on_hyperv(struct ixgbe_hw *hw)
> > > +{
> > > + if (hw->mbx.ops.check_for_msg == NULL)
> > > + return true;
> > > + else
> > > + return false;
> > > +}
trivia:
bool func(...)
{
if (<bar>)
return true;
else
return false;
}
can generally be written as:
bool func(...)
{
return <bar>;
}
next prev parent reply other threads:[~2016-04-18 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 5:22 [PATCH net-next V2 0/2] ethernet: intel: Support Hyper-V hosts K. Y. Srinivasan
2016-04-18 5:22 ` K. Y. Srinivasan
2016-04-18 5:22 ` [PATCH net-next V2 1/2] ethernet: intel: Add the device ID's presented while running on Hyper-V K. Y. Srinivasan
2016-04-18 5:22 ` [PATCH net-next V2 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V) K. Y. Srinivasan
2016-04-18 16:17 ` [Intel-wired-lan] " Alexander Duyck
2016-04-18 16:52 ` KY Srinivasan
2016-04-18 17:00 ` Joe Perches [this message]
2016-04-18 19:42 ` KY Srinivasan
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=1460998819.1917.10.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.duyck@gmail.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=eli@mellanox.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jackm@mellanox.com \
--cc=jasowang@redhat.com \
--cc=john.ronciak@intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=yevgenyp@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome