linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: wang.yi59@zte.com.cn
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
	ard.biesheuvel@linaro.org, linux-efi@vger.kernel.org,
	pbonzini@redhat.com, rkrcmar@redhat.com, kvm@vger.kernel.org,
	jgross@suse.com, akataria@vmware.com,
	virtualization@lists.linux-foundation.org,
	m.mizuma@jp.fujitsu.com, peterz@infradead.org, prarit@redhat.com,
	douly.fnst@cn.fujitsu.com, dwmw@amazon.co.uk, luto@kernel.org,
	pasha.tatashin@oracle.com, rajvi.jingar@intel.com,
	zhe.he@windriver.com, akpm@linux-foundation.org,
	dyoung@redhat.com, takahiro.akashi@linaro.org,
	ebiederm@xmission.com, bhe@redhat.com, ivan.gorinov@intel.com,
	robh@kernel.org, andy.shevchenko@gmail.com,
	frank.rowand@sony.com, jan.kiszka@siemens.com,
	jailhouse-dev@googlegroups.com, konrad.wilk@oracle.com,
	thomas.lendacky@amd.com, pravin.shedge4linux@gmail.com,
	namit@vmware.com, jroedel@suse.de, bhelgaas@google.com,
	linux-pci@vger.kernel.org, keescook@chromium.org,
	anton@enomsg.org, ccross@android.com, tony.luck@intel.com,
	rostedt@goodmis.org, kexec@lists.infradead.org,
	robh+dt@kernel.org, frowand.list@gmail.com,
	devicetree@vger.kernel.org, oleg@redhat.com,
	zhong.weidong@zte.com.cn, up2wing@gmail.com
Subject: Re: [PATCH] x86: fix -Wmissing-prototypes warning
Date: Thu, 22 Nov 2018 12:14:58 +0100	[thread overview]
Message-ID: <20181122111458.GA107823@gmail.com> (raw)
In-Reply-To: <201811221904598072830@zte.com.cn>


* wang.yi59@zte.com.cn <wang.yi59@zte.com.cn> wrote:

> Hi Ingo,
> 
> > * Yi Wang <wang.yi59@zte.com.cn> wrote:
> >
> > > We may get -Wmissing-prototypes warnings when building
> > > kernel with W=1, it's better to fix them as global function
> > > signature can be changed and caller who use the old unchanged
> > > prototypes will be hosed.
> > >
> > > This patch fixes most of -Wmissing-prototypes warnings which
> > > are in the root directory of arch/x86/kernel, not including
> > > the subdirectories.
> > >
> > > These are the warnings fixed in this patch:
> > > arch/x86/kernel/signal.c:865:17: warning: no previous prototype for ‘sys32_x32_rt_sigreturn’ [-Wmissing-prototypes]
> 
> ......
> 
> > >  include/linux/ftrace.h             | 3 +++
> > >  include/linux/kexec.h              | 1 +
> > >  include/linux/of_fdt.h             | 1 +
> > >  include/linux/ptrace.h             | 1 +
> > >  24 files changed, 55 insertions(+), 3 deletions(-)
> >
> > Breaks 32-bit compilation:
> >
> > ../arch/x86/include/asm/setup.h: Assembler messages:
> > ../arch/x86/include/asm/setup.h:30: Error: no such instruction: `unsigned long __startup_64(unsigned long physaddr,struct boot_params *bp)'
> >
> > I'll skip the setup.h bits - let's hope that's the only bug.
> 
> Sorry for the inconvenience, though I have checked carefully :-)
> 
> How do you produce this error? I tested this way but did not reproduce
> that error:
> # make allmodconfig
> # make -j8
> 
> Thanks for your time again!

I don't remember the exact config, but you could try the 32-bit 
allnoconfig and defconfig.

Note that the commands you used above will use the 64-bit kernel, not the 
32-bit kernel.

Thanks,

	Ingo

  parent reply	other threads:[~2018-11-22 11:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  2:04 [PATCH] x86: fix -Wmissing-prototypes warning Yi Wang
2018-11-22  8:48 ` Ingo Molnar
     [not found]   ` <201811221904598072830@zte.com.cn>
2018-11-22 11:14     ` Ingo Molnar [this message]
2018-11-22 10:15 ` [tip:x86/cleanups] x86/headers: Fix " tip-bot for Yi Wang
2018-11-23  7:03   ` Ingo Molnar
2018-11-23  7:04 ` tip-bot for Yi Wang

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=20181122111458.GA107823@gmail.com \
    --to=mingo@kernel.org \
    --cc=akataria@vmware.com \
    --cc=akpm@linux-foundation.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=anton@enomsg.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=ccross@android.com \
    --cc=devicetree@vger.kernel.org \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=dwmw@amazon.co.uk \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=frank.rowand@sony.com \
    --cc=frowand.list@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ivan.gorinov@intel.com \
    --cc=jailhouse-dev@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jgross@suse.com \
    --cc=jroedel@suse.de \
    --cc=keescook@chromium.org \
    --cc=kexec@lists.infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=m.mizuma@jp.fujitsu.com \
    --cc=mingo@redhat.com \
    --cc=namit@vmware.com \
    --cc=oleg@redhat.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=prarit@redhat.com \
    --cc=pravin.shedge4linux@gmail.com \
    --cc=rajvi.jingar@intel.com \
    --cc=rkrcmar@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tony.luck@intel.com \
    --cc=up2wing@gmail.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wang.yi59@zte.com.cn \
    --cc=x86@kernel.org \
    --cc=zhe.he@windriver.com \
    --cc=zhong.weidong@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).