From: Andrew Morton <akpm@linux-foundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [next:akpm 202/376] arch/sh/kernel/ioport.c:14:15: error: conflicting type qualifiers for 'sh_io
Date: Fri, 21 Sep 2012 19:33:53 +0000 [thread overview]
Message-ID: <20120921123353.b1682e00.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120921105635.GA13728@localhost>
On Fri, 21 Sep 2012 07:51:53 -0700
Andi Kleen <ak@linux.intel.com> wrote:
> On Fri, Sep 21, 2012 at 06:56:35PM +0800, Fengguang Wu wrote:
> > Hi Andi,
> >
> > FYI, kernel build failed on
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
> > head: 69921c36f9e0e4e7952fa2583bf2d33713835eaf
> > commit: 11f7c1c694b94586a232a50eebdd623255d60d72 [202/376] sections: fix section conflicts in arch/sh
> > config: sh-titan_defconfig
>
> Does this patch work?
>
> diff --git a/arch/sh/include/asm/io.h b/arch/sh/include/asm/io.h
> index 0cf60a6..73a23f4 100644
> --- a/arch/sh/include/asm/io.h
> +++ b/arch/sh/include/asm/io.h
> @@ -134,7 +134,7 @@ __BUILD_MEMORY_STRING(__raw_, q, u64)
> * load/store instructions. sh_io_port_base is the virtual address to
> * which all ports are being mapped.
> */
> -extern const unsigned long sh_io_port_base;
> +extern unsigned long sh_io_port_base;
>
> static inline void __set_io_port_base(unsigned long pbase)
> {
yup.
prev parent reply other threads:[~2012-09-21 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 10:56 [next:akpm 202/376] arch/sh/kernel/ioport.c:14:15: error: conflicting type qualifiers for 'sh_io_por Fengguang Wu
2012-09-21 14:51 ` [next:akpm 202/376] arch/sh/kernel/ioport.c:14:15: error: conflicting type qualifiers for 'sh_io Andi Kleen
2012-09-21 19:33 ` Andrew Morton [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=20120921123353.b1682e00.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.