From mboxrd@z Thu Jan  1 00:00:00 1970
From: KY Srinivasan <kys@microsoft.com>
Subject: RE: linux-next: build warning after merge of the char-misc tree
Date: Thu, 20 Jul 2017 14:52:38 +0000
Message-ID: <DM5PR21MB04766E7EE73ABDD8E17CFF7AA0A70@DM5PR21MB0476.namprd21.prod.outlook.com>
References: <20170720141203.53dff686@canb.auug.org.au>
 <20170720051324.GA8168@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20170720051324.GA8168@kroah.com>
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
To: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Linux-Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Vitaly Kuznetsov <vkuznets@redhat.com>, Andy Shevchenko <andy.shevchenko@gmail.com>
List-Id: linux-next.vger.kernel.org



> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Wednesday, July 19, 2017 10:13 PM
> To: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Arnd Bergmann <arnd@arndb.de>; Linux-Next Mailing List <linux-
> next@vger.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>; Vitaly Kuznetsov <vkuznets@redhat.com>; KY
> Srinivasan <kys@microsoft.com>; Andy Shevchenko
> <andy.shevchenko@gmail.com>
> Subject: Re: linux-next: build warning after merge of the char-misc tree
>=20
> On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, yesterday's linux-next build (i386
> > defconfig) produced this warning:
> >
> > In file included from
> /home/sfr/next/next/arch/x86/entry/vdso/vma.c:25:0:
> > /home/sfr/next/next/arch/x86/include/asm/mshyperv.h:181:15: warning:
> return type defaults to 'int' [-Wreturn-type]
> >  static inline hyperv_cleanup(void) {}
> >                ^
> >
> > Introduced by commit
> >
> >   2e252fbf777d ("x86/hyper-v: include hyperv/ only when CONFIG_HYPERV
> is set")
>=20
> Ugh, KY, can you send me a fix for this?

I just saw that you reverted the patch. We will fix this up and resend.

Thanks,

K. Y
>=20
> All of these gcc-7 warnings are keeping me from seeing the "real"
> problems now :(
>=20
> thanks,
>=20
> greg k-h