public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V5 1/1] gdb: Upgrade 16.3 -> 17.1
Date: Mon, 16 Mar 2026 10:01:01 -0700	[thread overview]
Message-ID: <411950.1773680461337707635@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_yj4wubgwkd+2uvkQ_p=ZXGc-MVhRcrHEdd6AM7JaDwQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

On Mon, Mar 16, 2026 at 04:29 PM, Alexander Kanavin wrote:

> 
> But Pending is not an appropriate status here, as
> it means something is preventing the patch from being submitted, or it
> isn't clear whether it should be submitted

Hi Alex,

Thanks for the Feedback.
You're right — "Pending" isn't the best fit here. The patch is a partial adaptation/backport of
Thiago Jung Bauermann’s V4 series, which is still under review on gdb-patches and has not
landed in master yet. ( https://sourceware.org/pipermail/gdb-patches/2026-March/225502.html )

Thiago has indicated he will prepare a 17.1-specific version once the master series is resolved.

I’ve updated the Upstream-Status line to:

Upstream-Status: Submitted [gdb-patches, Thiago Jung Bauermann v4 series (not yet merged): https://sourceware.org/pipermail/gdb-patches/2026-March/225502.html — partial adaptation for the GDB 17.1 header layout]

Would you prefer using Backport [...] here instead, even though there is no master commit yet,
or does Submitted better reflect the current upstream situation?

Thanks,
Sunil Dora

[-- Attachment #2: Type: text/html, Size: 1294 bytes --]

  reply	other threads:[~2026-03-16 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  4:09 [PATCH V5 0/1] gdb: upgrade to 17.1 sunilkumar.dora
2026-03-16  4:09 ` [PATCH V5 1/1] gdb: Upgrade 16.3 -> 17.1 sunilkumar.dora
2026-03-16 10:59   ` [OE-core] " Alexander Kanavin
2026-03-16 17:01     ` Dora, Sunil Kumar [this message]
2026-03-16 17:13       ` Alexander Kanavin
2026-03-17  6:34         ` Dora, Sunil Kumar

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=411950.1773680461337707635@lists.openembedded.org \
    --to=sunilkumar.dora@windriver.com \
    --cc=openembedded-core@lists.openembedded.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