From: Andrew Morton <akpm@linux-foundation.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
LKML <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Richard Henderson <rth@twiddle.net>,
tony.luck@intel.com, anton@samba.org, paulus@samba.org,
rusty@rustcorp.com.au
Subject: Re: [BUID_FAILURE] regression from 2.6.24-git18 to 2.6.25-rc1-git1 on section type conflict psmouse-base
Date: Mon, 11 Feb 2008 23:59:29 -0800 [thread overview]
Message-ID: <20080211235929.791f7afb.akpm@linux-foundation.org> (raw)
In-Reply-To: <47B14D52.6050404@linux.vnet.ibm.com>
On Tue, 12 Feb 2008 13:10:02 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> This build failure is seen on the powerpc from the 2.6.24-git18 kernel and is still visible
> in the 2.6.25-rc1-git1.
>
> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
> make[3]: *** [drivers/input/mouse/psmouse-base.o] Error 1
> make[2]: *** [drivers/input/mouse] Error 2
> make[1]: *** [drivers/input] Error 2
>
> The patch http://lkml.org/lkml/2008/2/8/514 seems to have not taken into 2.6.25-rc1 and
> 2.6.25-rc1-git(s). Is there any new patch i am missing out.
I have it queued up, along with quite a few other things, but for the next
couple of days I have logistical problems which are preventing me from
doing runtime testing.
next prev parent reply other threads:[~2008-02-12 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 7:40 [BUID_FAILURE] regression from 2.6.24-git18 to 2.6.25-rc1-git1 on section type conflict psmouse-base Kamalesh Babulal
2008-02-12 7:59 ` Andrew Morton [this message]
2008-02-12 9:36 ` Adrian Bunk
2008-02-12 9:47 ` Kamalesh Babulal
2008-02-12 9:55 ` Adrian Bunk
2008-02-12 12:10 ` Kamalesh Babulal
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=20080211235929.791f7afb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=bunk@kernel.org \
--cc=ink@jurassic.park.msu.ru \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--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