From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, debian-kernel@lists.debian.org
Subject: Re: Two 32bit power3/4 build-failure patches ...
Date: Mon, 17 Oct 2005 08:43:03 +1000 [thread overview]
Message-ID: <1129502584.7620.37.camel@gaston> (raw)
In-Reply-To: <20051016102828.GA32332@localhost.localdomain>
On Sun, 2005-10-16 at 12:28 +0200, Sven Luther wrote:
> Hello,
>
> I have here two 32bit power[34] build failure patches that the debian kernels
> has been using for some time, and which i think i did post here in the past,
> but it doesn't seem to be applied.
>
> Well, those are 32 bit issues, and debian doesn't build anymore 32bit kernels
> of those flavours, but i guess it may be possible that some random user wants
> to build them, so it would be nice if they could be included upstream.
I think we'll be dropping 64 bits CPU support for 32 bits kernel anyway.
Ben.
next prev parent reply other threads:[~2005-10-16 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 10:28 Two 32bit power3/4 build-failure patches Sven Luther
2005-10-16 22:43 ` Benjamin Herrenschmidt [this message]
2005-10-16 22:54 ` Sven Luther
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=1129502584.7620.37.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=debian-kernel@lists.debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sven.luther@wanadoo.fr \
/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;
as well as URLs for NNTP newsgroup(s).