From: Thomas Gleixner <tglx@linutronix•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Ingo Molnar <mingo@elte•hu>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build warning from Linus' tree
Date: Fri, 30 Aug 2019 00:29:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908300028360.1938@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190830082357.4650d243@canb.auug.org.au>
Stephen,
On Fri, 30 Aug 2019, Stephen Rothwell wrote:
> Hi all,
>
> From Linus tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> arch/x86/boot/edd.c: In function 'query_edd':
> arch/x86/boot/edd.c:148:11: warning: taking address of packed member of 'struct boot_params' may result in an unaligned pointer value [-Waddress-of-packed-member]
> 148 | mbrptr = boot_params.edd_mbr_sig_buffer;
> | ^~~~~~~~~~~
>
> I assume this is a result of upgrading my x86_64 cross compiler to v9.2.1
> (from v8.3.0).
Yes. We have a fix queued which should hit next tomorrow.
Thanks,
tglx
next prev parent reply other threads:[~2019-08-29 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 22:23 linux-next: build warning from Linus' tree Stephen Rothwell
2019-08-29 22:29 ` Thomas Gleixner [this message]
2019-08-30 0:25 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 7:20 Stephen Rothwell
2021-07-08 2:25 ` Stephen Rothwell
2021-07-20 7:31 ` Stephen Rothwell
2021-08-10 9:29 ` Stephen Rothwell
2017-02-26 23:23 Stephen Rothwell
2011-06-03 1:10 Stephen Rothwell
2011-06-03 14:17 ` David Sterba
2011-06-03 1:00 Stephen Rothwell
2010-10-27 0:29 Stephen Rothwell
2010-10-27 0:58 ` Jesse Gross
2010-10-27 0:00 Stephen Rothwell
2010-09-24 4:08 Stephen Rothwell
2010-09-24 12:32 ` Frederic Weisbecker
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=alpine.DEB.2.21.1908300028360.1938@nanos.tec.linutronix.de \
--to=tglx@linutronix$(echo .)de \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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