From: Michael Ellerman <mpe@ellerman.id.au>
To: Joseph Myers <joseph@codesourcery.com>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
"David S.Miller" <davem@davemloft.net>,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com
Subject: Re: [PATCH RESEND] Update kernel math-emu code from current glibc soft-fp
Date: Wed, 01 Jul 2015 08:18:05 +1000 [thread overview]
Message-ID: <1435702685.24693.3.camel@ellerman.id.au> (raw)
In-Reply-To: <alpine.DEB.2.10.1506301042250.2339@digraph.polyomino.org.uk>
On Tue, 2015-06-30 at 10:48 +0000, Joseph Myers wrote:
> On Tue, 30 Jun 2015, Michael Ellerman wrote:
>
> > Is there some way you can imagine of splitting this up into smaller chunks, so
> > that different arches can merge the pieces separately?
>
> Well, it could be split as:
>
> 1. Rename include/math-emu to math-emu-old and update architectures for
> the renaming (mechanically).
>
> 2. Add new include/math-emu.
>
> 3,4,5,6,7. Move each architecture from math-emu-old to math-emu.
>
> 8. Remove math-emu-old.
>
> You still have patch 1 affecting all five architectures, but with the
> per-architecture changes being much simpler.
OK. That's obviously a bit more churn, but I think it's probably the best
approach. Unless someone else has a better idea?
cheers
next prev parent reply other threads:[~2015-06-30 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 22:16 [PATCH] Update kernel math-emu code from current glibc soft-fp Joseph Myers
2015-06-22 13:26 ` [PATCH RESEND] " Joseph Myers
2015-06-29 14:19 ` Ping " Joseph Myers
2015-06-30 3:28 ` Michael Ellerman
2015-06-30 10:48 ` Joseph Myers
2015-06-30 22:18 ` Michael Ellerman [this message]
2015-07-01 7:34 ` Geert Uytterhoeven
2015-07-02 12:50 ` Michael Ellerman
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=1435702685.24693.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=joseph@codesourcery.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=schwidefsky@de.ibm.com \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox