From: Keith Seitz <keiths@redhat.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] cleanup: Add missing feature/ XML files to Makefile
Date: Thu, 29 Sep 2022 10:08:05 -0700 [thread overview]
Message-ID: <84849fff-9739-3d77-ac04-d3f68f4acfa8@redhat.com> (raw)
In-Reply-To: <3b7b0389-3cfe-ea44-7a22-9cb496debd4c@simark.ca>
On 9/27/22 17:37, Simon Marchi wrote:
>
> On 2022-09-27 13:57, Keith Seitz wrote:
>> On 9/13/22 06:55, Keith Seitz via Gdb-patches wrote:
>>> On 9/13/22 06:34, Simon Marchi wrote:
>>>> aarch64-sve.c is not generate, so it's actually fine. cskyv2-linux.c is
>>>> generated, but we are missing the XML for it, I sent a reply to the
>>>> patch thread that added it to ask the author to upload it.
>>>
>>> Bah. I caught aarch64-sve.c, but not the other. Thank you for catching that.
>>> I will keep my eye out for it and update when cskyv2-linux.xml reappears.
>>
>> cskyv2-linux.xml has landed. Is there anything else I need to address before
>> pushing this?
>
> Not sure if you intended to omit gdb-patches on this, but in any case I think the patch
> is good to go.
I did not intend to omit the list, but it happened anyway. :-)
I've now pushed this. Thank you for the review.
Keith
prev parent reply other threads:[~2022-09-29 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 22:47 Keith Seitz
2022-09-12 22:47 ` [PATCH 2/2] Constify target_desc declarations Keith Seitz
2022-09-13 13:38 ` Simon Marchi
2022-09-13 13:34 ` [PATCH 1/2] cleanup: Add missing feature/ XML files to Makefile Simon Marchi
2022-09-13 13:55 ` Keith Seitz
2022-09-13 13:57 ` Simon Marchi
2022-09-13 14:44 ` Keith Seitz
2022-09-13 14:10 ` Luis Machado
2022-09-13 15:11 ` Simon Marchi
2022-09-13 15:19 ` Luis Machado
[not found] ` <2e6adda3-3cdf-7520-eee9-d58f179537ab@redhat.com>
[not found] ` <3b7b0389-3cfe-ea44-7a22-9cb496debd4c@simark.ca>
2022-09-29 17:08 ` Keith Seitz [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=84849fff-9739-3d77-ac04-d3f68f4acfa8@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@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).