> -----Original Message----- > From: Joe Perches [mailto:j...@perches.com] > Sent: Monday, April 18, 2016 10:00 AM > To: KY Srinivasan <k...@microsoft.com>; Alexander Duyck > <alexander.du...@gmail.com> > Cc: David Miller <da...@davemloft.net>; Netdev > <netdev@vger.kernel.org>; linux-ker...@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; Robo Bot > <a...@canonical.com>; Jason Wang <jasow...@redhat.com>; > e...@mellanox.com; ja...@mellanox.com; yevge...@mellanox.com; John > Ronciak <john.ronc...@intel.com>; intel-wired-lan <intel-wired- > l...@lists.osuosl.org> > Subject: Re: [Intel-wired-lan] [PATCH net-next V2 2/2] intel: ixgbevf: Support > Windows hosts (Hyper-V) > > 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>; > }
Thanks Joe; will update. K. Y
