From: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
To: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Reference array of structs instead of first member during memcpy
Date: Tue, 25 Jan 2022 14:44:14 -0700 [thread overview]
Message-ID: <20220125144414.23457be3@f35-zws-1> (raw)
In-Reply-To: <20220125163900.800317-1-keiths@redhat.com>
On Tue, 25 Jan 2022 08:39:00 -0800
Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> wrote:
> The simple fix is to reference the array, `MEMS' as the destination of the copy.
LGTM.
Kevin
next prev parent reply other threads:[~2022-01-25 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:39 Keith Seitz via Gdb-patches
2022-01-25 21:44 ` Kevin Buettner via Gdb-patches [this message]
2022-01-26 17:31 ` Keith Seitz via Gdb-patches
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=20220125144414.23457be3@f35-zws-1 \
--to=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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