All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "Oliver O'Halloran" <oohall@gmail.com>,
	linuxppc-dev@lists.ozlabs.org,
	Nicholas Piggin <npiggin@gmail.com>,
	Alan Modra <amodra@gmail.com>
Subject: Re: [RFC][PATCH] powerpc/64be: use ELFv2 ABI for big endian kernels
Date: Fri, 25 Nov 2016 08:59:24 -0600	[thread overview]
Message-ID: <20161125145923.GA32415@gate.crashing.org> (raw)
In-Reply-To: <877f7stiy5.fsf@concordia.ellerman.id.au>

On Fri, Nov 25, 2016 at 01:02:58PM +1100, Michael Ellerman wrote:
> Because we're hairy chested kernel programmers we don't actually build a
> C library at all. So we don't get that hint that we're using an odd
> combination, we just configure the toolchain, build it and off we go.

Right, I keep forgetting that kernel developers never read any
documentation either :-P


Segher

      reply	other threads:[~2016-11-25 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 13:08 [RFC][PATCH] powerpc/64be: use ELFv2 ABI for big endian kernels Nicholas Piggin
2016-11-23 14:20 ` Balbir Singh
2016-11-23 14:38 ` Segher Boessenkool
2016-11-24  4:42   ` Nicholas Piggin
2016-11-24  5:37   ` Oliver O'Halloran
2016-11-24 12:27     ` Segher Boessenkool
2016-11-24 22:22       ` Michael Ellerman
2016-11-24 23:17         ` Segher Boessenkool
2016-11-25  1:13           ` Nicholas Piggin
2016-11-25  2:08             ` Michael Ellerman
2016-11-25  2:35               ` Nicholas Piggin
2016-11-25  3:35                 ` Michael Ellerman
2016-11-25  2:02           ` Michael Ellerman
2016-11-25 14:59             ` Segher Boessenkool [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=20161125145923.GA32415@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=amodra@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    /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.