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: Tue, 4 Mar 2008 13:35:04 +1100 [thread overview]
Message-ID: <200803041335.05144.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080303081345.GA4457@cs181133002.pp.htv.fi>
On Monday 03 March 2008 19:13:45 Adrian Bunk wrote:
> On Mon, Mar 03, 2008 at 03:35:16PM +1100, Rusty Russell wrote:
> > 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?
>
> We should have caught all architectures having problems, and a slightly
> improved patch is now in Linus' tree.
Yes, thanks, I saw it later on in the thread. 'Tis still horrible tho :)
Rusty.
prev parent reply other threads:[~2008-03-04 2: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
2008-03-03 8:13 ` Adrian Bunk
2008-03-04 2:35 ` Rusty Russell [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=200803041335.05144.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.