public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	Wei Liu <wei.liu@kernel.org>
Subject: Re: linux-next: Tree for Aug 23 (hyperv)
Date: Thu, 24 Aug 2023 03:14:58 +0000	[thread overview]
Message-ID: <ZObLMtemsJap3UX+@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <449fdf75-6d5c-46c3-2a1e-23c55a73b62e@infradead.org>

On Wed, Aug 23, 2023 at 06:45:07PM -0700, Randy Dunlap wrote:
> 
> 
> On 8/22/23 23:14, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20230822:
> > 
> 
> on x86_64:
> 
> In file included from ../arch/x86/hyperv/hv_init.c:20:
> ../arch/x86/include/asm/mshyperv.h:272:12: warning: 'hv_snp_boot_ap' defined but not used [-Wunused-function]
>   272 | static int hv_snp_boot_ap(int cpu, unsigned long start_ip) { return 0; }
>       |            ^~~~~~~~~~~~~~
[...]
> 
> Full randconfig file is attached.

Thanks for the email.

I think this is already fixed in hyperv-next. In the latest code,
hv_snp_boot_ap in has `inline` attribute.

Thanks,
Wei.

> -- 
> ~Randy



  reply	other threads:[~2023-08-24  3:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  6:14 linux-next: Tree for Aug 23 Stephen Rothwell
2023-08-24  1:32 ` linux-next: Tree for Aug 23 (arch/loongarch/mm/kasan_init.o) Randy Dunlap
2023-08-24  1:35 ` linux-next: Tree for Aug 23 (drivers/perf/arm_pmuv3.o) Randy Dunlap
2023-08-24  1:38 ` linux-next: Tree for Aug 23 (drivers/iio/imu/bno055/bno055.o) Randy Dunlap
2023-08-24  1:45 ` linux-next: Tree for Aug 23 (hyperv) Randy Dunlap
2023-08-24  3:14   ` Wei Liu [this message]
2023-08-24  4:33     ` Randy Dunlap
2023-08-24  2:06 ` linux-next: Tree for Aug 23 (drivers/platform/x86/amd/pmc.c) Randy Dunlap
2023-08-26 10:09   ` Hans de Goede

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=ZObLMtemsJap3UX+@liuwe-devbox-debian-v2 \
    --to=wei.liu@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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