From: Michal Marek <mmarek@suse.cz>
To: Ben Hutchings <ben@decadent.org.uk>, Michael Neuling <mikey@neuling.org>
Cc: linux-kbuild@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>,
Leann Ogasawara <leann.ogasawara@canonical.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH v2] deb-pkg: Add support for powerpc little endian
Date: Fri, 12 Sep 2014 16:12:21 +0200 [thread overview]
Message-ID: <5412FF45.30208@suse.cz> (raw)
In-Reply-To: <1410057728.7389.24.camel@decadent.org.uk>
On 2014-09-07 04:42, Ben Hutchings wrote:
> On Fri, 2014-09-05 at 09:09 -0300, Thadeu Lima de Souza Cascardo wrote:
>> On Fri, Sep 05, 2014 at 05:55:18PM +1000, Michael Neuling wrote:
>>> On Fri, 2014-09-05 at 09:13 +0200, Gabriel Paubert wrote:
>>>> On Fri, Sep 05, 2014 at 03:28:47PM +1000, Michael Neuling wrote:
>>>>> The Debian powerpc little endian architecture is called ppc64le. This
>>>>
>>>> Huh? ppc64le or ppc64el?
>>>
>>> ppc64el. Commit message is wrong. Fixed below.
>>>
>>> Mikey
>>>
>>>
>>
>> What about ppc64?
>>
>> Also, I sent that already a month ago. Both linuxppc-dev and Michal
>> Marek were on cc.
>>
>> http://marc.info/?l=linux-kernel&m=140744360328562&w=2
>
> Anyone using powerpc (32-bit) will then need to add ppc64 as a foreign
> architecture before they can install a 64-bit custom kernel. This is
> fine in principle, except that ppc64 is not an official Debian port and
> its packages are not mirrored on the same servers.
[...]
> So I think Michael's version, leaving big-endian kernels as powerpc by
> default, is preferable for now.
I applied v2 of Michael's patch to kbuild.git#misc.
Michal
next prev parent reply other threads:[~2014-09-12 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 5:28 deb-pkg: Add support for powerpc little endian Michael Neuling
2014-09-05 7:13 ` Gabriel Paubert
2014-09-05 7:55 ` [PATCH v2] " Michael Neuling
2014-09-05 12:09 ` Thadeu Lima de Souza Cascardo
2014-09-07 2:42 ` Ben Hutchings
2014-09-12 14:12 ` Michal Marek [this message]
2014-09-05 12:14 ` Josh Boyer
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=5412FF45.30208@suse.cz \
--to=mmarek@suse.cz \
--cc=anton@samba.org \
--cc=ben@decadent.org.uk \
--cc=cascardo@linux.vnet.ibm.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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 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).