From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, linuxppc-dev@lists.ozlabs.org,
Steve Munroe <munroesj@linux.vnet.ibm.com>
Subject: Re: [PATCH] Add hwcap2 bits for POWER9
Date: Mon, 11 Jan 2016 13:16:37 -0200 [thread overview]
Message-ID: <87wprgdu3u.fsf@totoro.br.ibm.com> (raw)
In-Reply-To: <568FE3D0.7080008@linaro.org> (Adhemerval Zanella's message of "Fri, 8 Jan 2016 14:29:04 -0200")
Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> On 08-01-2016 13:36, Peter Bergner wrote:
>> On Fri, 2016-01-08 at 11:25 -0200, Tulio Magno Quites Machado Filho wrote:
>>> Peter, this solves the issue you reported previously [1].
>>>
>>> [1] https://sourceware.org/ml/libc-alpha/2015-12/msg00522.html
>>
>> Agreed, thanks. I'll also add the POWER9 support to the GCC side
>> of the patch now that the glibc code is upstream.
>
> I do not see these bits being added in kernel side yet and GLIBC usual
> only sync these kind of bits *after* they are included in kernel side.
> So I would advise to either get these pieces (kernel support and hwcap
> advertise) in kernel before 2.23 release, otherwise revert the patches.
Ack.
It has just been sent to the correspondent Linux mailing list:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-January/137763.html
--
Tulio Magno
next parent reply other threads:[~2016-01-11 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <568C272D.6000705@linux.vnet.ibm.com>
[not found] ` <87egdsi4om.fsf@totoro.br.ibm.com>
[not found] ` <1452267366.5201.12.camel@vnet.ibm.com>
[not found] ` <568FE3D0.7080008@linaro.org>
2016-01-11 15:16 ` Tulio Magno Quites Machado Filho [this message]
2016-01-11 15:21 ` [PATCH] Add hwcap2 bits for POWER9 Carlos O'Donell
2016-01-11 19:55 ` Tulio Magno Quites Machado Filho
2016-01-11 20:48 ` Carlos O'Donell
2016-01-12 16:39 ` Steven Munroe
2016-01-12 17:45 ` Carlos O'Donell
2016-01-15 23:09 ` Michael Ellerman
2016-01-15 22:30 ` Carlos Eduardo Seo
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=87wprgdu3u.fsf@totoro.br.ibm.com \
--to=tuliom@linux.vnet.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=munroesj@linux.vnet.ibm.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 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).