From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
"Carlos O'Donell" <carlos@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
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: Fri, 15 Jan 2016 20:30:44 -0200 [thread overview]
Message-ID: <56997314.9060102@linux.vnet.ibm.com> (raw)
In-Reply-To: <87bn8revra.fsf@totoro.br.ibm.com>
On 1/11/16 5:55 PM, Tulio Magno Quites Machado Filho wrote:
>
> However, I do agree with the concerns raised by Peter and Adhemerval: glibc
> should be in sync with the kernel by the time of the release in order to
> guarantee both bits are reserved for the exact same goal and we should have
> both AT_HWCAP and AT_PLATFORM supporting the new processor.
> With that said, I was planning to revert both commits d2de9ef7 and b1f19b8e
> if we don't get the kernel patch accepted into the powerpc tree in time for
> the release 2.23.
>
Kernel patch is in, commit f689b742f217b2ffe7925f8a6521b208ee995309
Regards,
--
Carlos Eduardo Seo
Software Engineer - Linux on Power Toolchain
cseo@linux.vnet.ibm.com
prev parent reply other threads:[~2016-01-15 22:30 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 ` [PATCH] Add hwcap2 bits for POWER9 Tulio Magno Quites Machado Filho
2016-01-11 15:21 ` 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 [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=56997314.9060102@linux.vnet.ibm.com \
--to=cseo@linux.vnet.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=munroesj@linux.vnet.ibm.com \
--cc=tuliom@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).