public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
To: "Guillermo E. Martinez via Libabigail"
	<libabigail@sourceware.org>, Dodji Seketeli <dodji@seketeli.org>
Subject: Re: [PATCH] ctf-reader: Improves performance to read CTF information from Linux kernel
Date: Fri, 29 Apr 2022 08:58:00 -0500	[thread overview]
Message-ID: <1724741.VLH7GnMWUR@sali> (raw)
In-Reply-To: <87sfpwf8ke.fsf@seketeli.org>

On Friday, April 29, 2022 6:11:29 AM CDT Dodji Seketeli wrote:
> Hello,
Hello Dodji,

> "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org> a
> écrit:
> 
> > Hello libabigail team,
> >
> > This patch is meant to improves the performance to extract  CTF
> > information from Linux kernel, it depends of:
> >
> > https://sourceware.org/pipermail/libabigail/2022q1/004262.html
> >
> > Feedback will be welcomed and appreciated as ever!,
> 
> I am sorry, but the patch doesn't apply to the current master branch
> anymore :-(
Sorry, hmmm my fault, I forget mention that patch:
    https://sourceware.org/pipermail/libabigail/2022q1/004262.html
depends on this:
   https://sourceware.org/pipermail/libabigail/2022q2/004279.html 
> Would you ple|ase refresh it on your tree and re-send it?
Sure, i will refresh this and its dependencies from master :-)

> Thanks.
Thanks!, 
guillermo





  reply	other threads:[~2022-04-29 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 16:08 Guillermo E. Martinez
2022-04-25 18:33 ` Guillermo E. Martinez
2022-04-27 22:16 ` [PATCH v2] " Guillermo E. Martinez
2022-04-29 11:11 ` [PATCH] " Dodji Seketeli
2022-04-29 13:58   ` Guillermo E. Martinez [this message]
2022-04-29 14:28   ` [PATCH v3] " Guillermo E. Martinez

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=1724741.VLH7GnMWUR@sali \
    --to=guillermo.e.martinez@oracle.com \
    --cc=dodji@seketeli.org \
    --cc=libabigail@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).