From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, Gopi Kumar Bulusu <gopi@sankhya.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
Michael Eager <eager@eagercon.com>
Subject: Re: [PATCH] gdb/MicroBlaze: Add support for native linux gdb
Date: Fri, 29 May 2026 11:01:07 -0400 [thread overview]
Message-ID: <6838cb4f-838c-49ee-bb08-5b16b8eea8c5@simark.ca> (raw)
In-Reply-To: <874ijq5knu.fsf@tromey.com>
On 5/29/26 10:56 AM, Tom Tromey wrote:
>>>>>> Gopi Kumar Bulusu <gopi@sankhya.com> writes:
>
>> Attached is a patch to add native linux support for gdb including
>> cache target support.
>
> Thanks for the patch.
>
> I read through it and have some nits. There's nothing very serious
> except this:
>
>> The original sources for the patch come from Xilinx/AMD Yocto git
>> repository (2025.2)
>
> Who wrote them and are they covered by the copyright assignment?
>
> This is the most important consideration, the patch can't land without
> this being clear.
This was the situation for the previous gdbserver submission:
https://inbox.sourceware.org/gdb-patches/dd63d676-f390-460a-8b80-55df3285575a@simark.ca/
Gopi, is the situation the same for this code?
Simon
next prev parent reply other threads:[~2026-05-29 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 11:32 Gopi Kumar Bulusu
2026-05-26 11:33 ` Gopi Kumar Bulusu
2026-05-29 14:56 ` Tom Tromey
2026-05-29 15:01 ` Simon Marchi [this message]
2026-06-01 6:30 ` Gopi Kumar Bulusu
2026-06-01 6:38 ` Gopi Kumar Bulusu
2026-06-02 0:28 ` Michael Eager
2026-06-02 5:05 ` [PATCH v2] " Gopi Kumar Bulusu
2026-06-11 0:39 ` Michael Eager
2026-06-11 1:19 ` Gopi Kumar Bulusu
2026-06-11 1:41 ` Simon Marchi
2026-06-11 1:44 ` Gopi Kumar Bulusu
2026-06-11 12:52 ` Michael Eager
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=6838cb4f-838c-49ee-bb08-5b16b8eea8c5@simark.ca \
--to=simark@simark.ca \
--cc=binutils@sourceware.org \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=gopi@sankhya.com \
--cc=tom@tromey.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