[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d3f23370907011552h5b3c96b9h208d5567e7a2a615@mail.gmail.com>
Date: Thu, 2 Jul 2009 08:52:27 +1000
From: John Williams <john.williams@...alogix.com>
To: microblaze-uclinux@...e.uq.edu.au
Cc: LKML <linux-kernel@...r.kernel.org>,
Remis Lima Baima <remis.developer@...glemail.com>,
Arnd Bergmann <arnd@...db.de>, John Linn <John.Linn@...inx.com>
Subject: Re: [microblaze-uclinux] [PATCH 03/11] microblaze: fall back on
generic header files for the ABI
Hi Michal, Arnd,
On Wed, Jul 1, 2009 at 9:34 PM, Michal Simek<monstr@...str.eu> wrote:
> Added to next branch for test.
>
> I had to do one change.
> Microblaze needs __kernel_mode_t as short.
>
> + I removed __kernel_size_t and I'll recompile toolchain
> for removing warning messages
We need to be a little bit mindful here regarding which of the
asm-generic changes we merge immediately.
Ones that do not change the ABI at all, but simply pull from
asm-generic instead of asm-microblaze are obviously fine (identical
structures, bitfields etc).
However, we've just "broken" the ABI in 2.6.31, if we merge further
ABI breakage in 2.6.32 it's more pain and confusion.
So, unless we can merge and validate this ABI breakage during the
2.6.31-rc cycle, I think we need to hold on changes that would break
the ABI again, so soon.
Longer term there will be a complete redo of glibc up to the latest
version, which will obviously require a new toolchain for users - I
think that is the right place to do the next round of ABI breakage.
Any thoughts?
John
--
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists