public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
To: libabigail@sourceware.org
Subject: Re: [PATCH v2] ctf-reader: Fix multiple var-decl in anonymous struct/uninons
Date: Mon, 25 Apr 2022 13:38:33 -0500	[thread overview]
Message-ID: <3171653.44csPzL39Z@sali> (raw)
In-Reply-To: <20220406165907.1474155-1-guillermo.e.martinez@oracle.com>

On Wednesday, April 6, 2022 11:59:07 AM CDT Guillermo E. Martinez wrote:
Hello libabigail team,

Any comment about this patch?

Thanks in advanced!,
Guillermo
 
> This patch avoid multiple inclusion of `var-decl' node for the same
> field in anonymous struct/union declaration in the abixml, e.g:
> 
>   struct uprobe_task {
>    union {
>     struct {
>      unsigned long vaddr;
>     };
> 
>     struct {
>      int dup_xol_work;
>     };
>    };
>   };
> [...]



  reply	other threads:[~2022-04-25 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  5:20 [PATCH] " Guillermo E. Martinez
2022-04-06 16:59 ` [PATCH v2] " Guillermo E. Martinez
2022-04-25 18:38   ` Guillermo E. Martinez [this message]
2022-04-29 14:05   ` [PATCH v3] " Guillermo E. Martinez
2022-05-02 15:51     ` Dodji Seketeli

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=3171653.44csPzL39Z@sali \
    --to=guillermo.e.martinez@oracle.com \
    --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).