From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ralf Baechle <ralf@linux-mips•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Paul Burton <paul.burton@imgtec•com>
Subject: linux-next: build warnings after merge of the mips tree
Date: Wed, 12 Nov 2014 17:26:33 +1100 [thread overview]
Message-ID: <20141112172633.2b0c9cae@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3193 bytes --]
Hi Ralf,
After merging the mips tree, today's linux-next build (powerpc64
allnoconfig) produced these warnings:
In file included from fs/compat_binfmt_elf.c:145:0:
fs/binfmt_elf.c: In function 'load_elf_binary':
fs/binfmt_elf.c:718:13: warning: passing argument 1 of 'arch_elf_pt_proc' from incompatible pointer type
retval = arch_elf_pt_proc(&loc->elf_ex, elf_ppnt,
^
In file included from include/linux/elfcore-compat.h:4:0,
from fs/compat_binfmt_elf.c:20:
include/linux/elf.h:81:19: note: expected 'struct elf64_hdr *' but argument is of type 'struct elf32_hdr *'
static inline int arch_elf_pt_proc(struct elfhdr *ehdr,
^
In file included from fs/compat_binfmt_elf.c:145:0:
fs/binfmt_elf.c:718:13: warning: passing argument 2 of 'arch_elf_pt_proc' from incompatible pointer type
retval = arch_elf_pt_proc(&loc->elf_ex, elf_ppnt,
^
In file included from include/linux/elfcore-compat.h:4:0,
from fs/compat_binfmt_elf.c:20:
include/linux/elf.h:81:19: note: expected 'struct elf64_phdr *' but argument is of type 'struct elf32_phdr *'
static inline int arch_elf_pt_proc(struct elfhdr *ehdr,
^
In file included from fs/compat_binfmt_elf.c:145:0:
fs/binfmt_elf.c:747:14: warning: passing argument 1 of 'arch_elf_pt_proc' from incompatible pointer type
retval = arch_elf_pt_proc(&loc->interp_elf_ex,
^
In file included from include/linux/elfcore-compat.h:4:0,
from fs/compat_binfmt_elf.c:20:
include/linux/elf.h:81:19: note: expected 'struct elf64_hdr *' but argument is of type 'struct elf32_hdr *'
static inline int arch_elf_pt_proc(struct elfhdr *ehdr,
^
In file included from fs/compat_binfmt_elf.c:145:0:
fs/binfmt_elf.c:747:14: warning: passing argument 2 of 'arch_elf_pt_proc' from incompatible pointer type
retval = arch_elf_pt_proc(&loc->interp_elf_ex,
^
In file included from include/linux/elfcore-compat.h:4:0,
from fs/compat_binfmt_elf.c:20:
include/linux/elf.h:81:19: note: expected 'struct elf64_phdr *' but argument is of type 'struct elf32_phdr *'
static inline int arch_elf_pt_proc(struct elfhdr *ehdr,
^
In file included from fs/compat_binfmt_elf.c:145:0:
fs/binfmt_elf.c:761:11: warning: passing argument 1 of 'arch_check_elf' from incompatible pointer type
retval = arch_check_elf(&loc->elf_ex, !!interpreter, &arch_state);
^
In file included from include/linux/elfcore-compat.h:4:0,
from fs/compat_binfmt_elf.c:20:
include/linux/elf.h:104:19: note: expected 'struct elf64_hdr *' but argument is of type 'struct elf32_hdr *'
static inline int arch_check_elf(struct elfhdr *ehdr, bool has_interp,
^
Probably introduced by commit 7b76fe94c0e4 ("binfmt_elf: allow arch
code to examine PT_LOPROC ... PT_HIPROC headers") and maybe the
preceeding commits as well.
binfmt_elf.c is included by compat_binfmt_elf.c after defining some
things to build the compat versions of things.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2014-11-12 6:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141112172633.2b0c9cae@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.burton@imgtec$(echo .)com \
--cc=ralf@linux-mips$(echo .)org \
/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