From: Michael Ellerman <mpe@ellerman.id.au>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
"David S.Miller" <davem@davemloft.net>
Cc: Joseph Myers <joseph@codesourcery.com>,
heiko.carstens@de.ibm.com, 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
Subject: Re: Ping Re: [PATCH 0/8] math-emu: Update kernel math-emu code from current glibc soft-fp
Date: Fri, 28 Aug 2015 13:38:35 +1000 [thread overview]
Message-ID: <1440733115.8076.6.camel@ellerman.id.au> (raw)
In-Reply-To: <20150827133102.77026410@mschwide>
On Thu, 2015-08-27 at 13:31 +0200, Martin Schwidefsky wrote:
> On Thu, 27 Aug 2015 13:12:05 +1000
> Michael Ellerman <mpe@ellerman.id.au> wrote:
> > On Wed, 2015-08-26 at 14:44 +0000, Joseph Myers wrote:
> > > On Thu, 20 Aug 2015, Michael Ellerman wrote:
> > > > I'm reluctant to proceed with merging them though until we've heard at least
> > > > *something* from the other maintainers.
> > >
> > > Ping again for the other-architecture maintainers (alpha, s390, sh,
> > > sparc)....
> >
> > OK I've put this whole series in a branch with the acks we have so far.
> >
> > I'll ask Stephen to put it in linux-next once 4.3-rc1 is out, and I'll ask
> > Linus to pull it for 4.4
> >
> > I haven't published the branch yet, so if the s390 and sparc maintainers want
> > to send me acks I'll rebase and add them.
>
> For the s390 parts:
> Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Thanks.
So we're just waiting on davem for an ack for arch/sparc :D
cheers
prev parent reply other threads:[~2015-08-28 3:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 15:44 [PATCH 0/8] math-emu: Update kernel math-emu code from current glibc soft-fp Joseph Myers
2015-08-19 14:39 ` Ping " Joseph Myers
2015-08-19 23:26 ` Michael Ellerman
2015-08-26 14:44 ` Joseph Myers
2015-08-26 14:49 ` Geert Uytterhoeven
2015-08-26 19:48 ` Richard Henderson
2015-08-27 3:12 ` Michael Ellerman
2015-08-27 11:31 ` Martin Schwidefsky
2015-08-28 3:38 ` Michael Ellerman [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=1440733115.8076.6.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;
as well as URLs for NNTP newsgroup(s).