All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Adrian Bunk <bunk@kernel.org>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [BUILD_FAILURE] 2.6.24-git18 build fails section type conflict psmouse-base
Date: Mon, 3 Mar 2008 15:35:16 +1100	[thread overview]
Message-ID: <200803031535.17644.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080208104851.GI7198@cs181133002.pp.htv.fi>

On Friday 08 February 2008 21:48:51 Adrian Bunk wrote:
> On Fri, Feb 08, 2008 at 04:02:59PM +0530, Kamalesh Babulal wrote:
> > 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 
> @Rusty:
> Can you look at this issue? It's a modules problem on 3 architectures.
>
> cu
> Adrian
>
> [1] http://lkml.org/lkml/2007/12/27/29

Erk... This is horrible, and arguably something gcc should try to deal with.  
How about we just drop the const and add a comment, rather than breaking one 
arch at a time?

Thanks,
Rusty.



  parent reply	other threads:[~2008-03-03  4:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 10:32 [BUILD_FAILURE] 2.6.24-git18 build fails section type conflict psmouse-base Kamalesh Babulal
2008-02-08 10:48 ` Adrian Bunk
2008-02-08 12:50   ` Kamalesh Babulal
2008-02-08 12:50     ` Kamalesh Babulal
2008-02-08 13:30     ` Adrian Bunk
2008-02-08 13:30       ` Adrian Bunk
2008-02-08 14:23       ` Kamalesh Babulal
2008-02-08 14:23         ` Kamalesh Babulal
2008-02-08 22:25       ` Ivan Kokshaysky
2008-03-03  4:35   ` Rusty Russell [this message]
2008-03-03  8:13     ` Adrian Bunk
2008-03-04  2:35       ` Rusty Russell

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=200803031535.17644.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=apw@shadowen.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bunk@kernel.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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.