From: "Willgerodt, Felix via Gdb-patches" <gdb-patches@sourceware.org>
To: John Baldwin <jhb@FreeBSD.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v3 00/13] Handle variable XSAVE layouts
Date: Fri, 20 May 2022 14:53:09 +0000 [thread overview]
Message-ID: <MN2PR11MB45668AE82E60B566A9643A3A8ED39@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <38ff35cd-f50a-5e2d-1d8c-f2490c8826e8@FreeBSD.org>
> -----Original Message-----
> From: John Baldwin <jhb@FreeBSD.org>
> Sent: Donnerstag, 19. Mai 2022 18:06
> To: Willgerodt, Felix <felix.willgerodt@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [PATCH v3 00/13] Handle variable XSAVE layouts
>
> On 5/19/22 8:42 AM, Willgerodt, Felix wrote:
> > Hi John,
>
> > Yes you can remove the Intel changelogs.
>
> Ok, I will trim those. Should I keep or drop the SOB trailers
> given that at least the log messages are now a bit different?
>
I don't have a strong opinion on that, I think it is fine to remove
them. GDB doesn't care about them afaik.
It would be nice to keep a co-authored field if significant parts
were taken from our patches. But you seem to have done that.
Regards,
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2022-05-20 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 21:05 John Baldwin
2022-05-03 21:05 ` [PATCH v3 01/13] x86: Add an x86_xsave_layout structure to handle " John Baldwin
2022-05-03 21:05 ` [PATCH v3 02/13] core: Support fetching TARGET_OBJECT_X86_XSAVE_LAYOUT from architectures John Baldwin
2022-05-03 21:05 ` [PATCH v3 03/13] nat/x86-cpuid.h: Add x86_cpuid_count wrapper around __get_cpuid_count John Baldwin
2022-05-03 21:05 ` [PATCH v3 04/13] x86 nat: Add helper functions to save the XSAVE layout for the host John Baldwin
2022-05-03 21:05 ` [PATCH v3 05/13] gdb: Update x86 FreeBSD architectures to support XSAVE layouts John Baldwin
2022-05-03 21:05 ` [PATCH v3 06/13] gdb: Support XSAVE layouts for the current host in the FreeBSD x86 targets John Baldwin
2022-05-03 21:05 ` [PATCH v3 07/13] gdb: Update x86 Linux architectures to support XSAVE layouts John Baldwin
2022-05-03 21:05 ` [PATCH v3 08/13] gdb: Support XSAVE layouts for the current host in the Linux x86 targets John Baldwin
2022-05-03 21:05 ` [PATCH v3 09/13] gdb: Use x86_xstate_layout to parse the XSAVE extended state area John Baldwin
2022-05-03 21:05 ` [PATCH v3 10/13] gdbserver: Add a function to set the XSAVE mask and size John Baldwin
2022-05-03 21:05 ` [PATCH v3 11/13] gdbserver: Refactor the legacy region within the xsave struct John Baldwin
2022-05-03 21:05 ` [PATCH v3 12/13] gdbserver: Read offsets of the XSAVE extended region via CPUID John Baldwin
2022-05-03 21:05 ` [PATCH v3 13/13] x86: Remove X86_XSTATE_SIZE and related constants John Baldwin
2022-05-10 10:48 ` [PATCH v3 00/13] Handle variable XSAVE layouts George, Jini Susan via Gdb-patches
2022-05-18 21:48 ` John Baldwin
2022-05-18 21:53 ` John Baldwin
2022-05-19 15:42 ` Willgerodt, Felix via Gdb-patches
2022-05-19 16:05 ` John Baldwin
2022-05-20 14:53 ` Willgerodt, Felix via Gdb-patches [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=MN2PR11MB45668AE82E60B566A9643A3A8ED39@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=felix.willgerodt@intel.com \
--cc=jhb@FreeBSD.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