public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Gustavo Romero <gromero@linux.vnet.ibm.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] ppc64: Add HTM SPRs support to readelf
Date: Mon, 24 Jul 2017 19:17:00 -0000	[thread overview]
Message-ID: <20170724191750.GF8002@stream> (raw)
In-Reply-To: <59760A2A.30606@linux.vnet.ibm.com>

On Mon, Jul 24, 2017 at 11:54:34AM -0300, Gustavo Romero wrote:
> On 21-07-2017 16:55, Mark Wielaard wrote:
> > This patch looks perfect, thanks.
> 
> Thanks for reviewing it!
>
> > We normally keep elf.h in sync with glibc.
> > Could you submit this elf.h change to libc-alpha@sourceware.org?
> > Then we resync elf.h from glibc to pull in the new constants.
> 
> It looks like glibc community won't review / push that change as it is in
> freeze for glibc 2.26 cut right now accordingly to [1].
> 
> If my understanding is correct, it's a blocker or my change can be pushed
> to elfutils and once glibc is open again (in about a week) I can submit
> this elf.h change to libc-alpha@sourceware.org?

Lets call it a soft-block :) It is just that I hate the files getting
out of sync. We risk using slightly differently named constants. It
looks like the 2.26 release will be next week, so hopefully the freeze
will be over end of this week.

Could you post the fix to libc-alpha already and then ping it next
week once the tree open up again? Then I'll push your patch to
elfutils.

Thanks,

Mark

  reply	other threads:[~2017-07-24 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 21:49 Gustavo Romero
2017-07-21 19:55 ` Mark Wielaard
2017-07-24 14:54   ` Gustavo Romero
2017-07-24 19:17     ` Mark Wielaard [this message]
2017-07-24 20:47       ` Gustavo Romero
2017-07-24 20:50         ` Gustavo Romero
2017-07-25 10:34           ` Mark Wielaard
2017-08-15 14:25             ` Gustavo Romero
2017-08-15 20:51               ` Mark Wielaard

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=20170724191750.GF8002@stream \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=gromero@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 read-only IMAP folder(s) and NNTP newsgroup(s).