From: Christoph Hellwig <hch@lst.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fix misc compiler warnings in the ia64 build
Date: Mon, 12 Aug 2019 23:52:07 +0200 [thread overview]
Message-ID: <20190812215207.GA21391@lst.de> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7F41C3D7@ORSMSX115.amr.corp.intel.com>
On Mon, Aug 12, 2019 at 09:47:40PM +0000, Luck, Tony wrote:
> > this little series fixes various warnings I see in ia64 builds.
>
> Applied. Thanks.
>
> [I assume you are using some up-to-date version of gcc that generates these
> warnings ... I'm not seeing them, but I'm still using a compiler from the stone
> age]
This is with the gcc 8.1 x86 to ia64 binary from
http://kernel.mirror.ac.za/tools/crosstool/ that I found recently. But
at least the fork.c and kprobes.c ones should probably show up with any
supported compiler, the switch ones are fairly new.
prev parent reply other threads:[~2019-08-12 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 6:55 fix misc compiler warnings in the ia64 build Christoph Hellwig
2019-08-12 6:55 ` [PATCH 1/4] ia64: annotate a switch fallthrough in ia64_do_signal Christoph Hellwig
2019-08-12 6:55 ` [PATCH 2/4] ia64: annotate switch fallthroughs in ia64_handle_unaligned Christoph Hellwig
2019-08-12 6:55 ` [PATCH 3/4] ia64/kprobes: remove the unused ia64_get_bsp_cfm function Christoph Hellwig
2019-08-12 6:55 ` [PATCH 4/4] kernel: only define task_struct_whitelist conditionally Christoph Hellwig
2019-08-12 21:47 ` fix misc compiler warnings in the ia64 build Luck, Tony
2019-08-12 21:52 ` Christoph Hellwig [this message]
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=20190812215207.GA21391@lst.de \
--to=hch@lst.de \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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