public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: cpuinfo: Linux 6.5: add AMD 0x8000001f EAX 14 debug_swap SEV-ES full debug state swap
Date: Thu, 31 Aug 2023 11:08:03 +0200	[thread overview]
Message-ID: <ZPBYc2ut2HAIWZCw@calimero.vinschen.de> (raw)
In-Reply-To: <55a6a662221998fa93a01eeb0832e39e510b9cd2.1693454909.git.Brian.Inglis@Shaw.ca>

Hi Brian,

nothing against the patch as such, but your subject line is not so nice.
As it becomes the commit message first line, it should be shorter.  Add
more descriptive text instead, please, and make sure that it tells the
reader what you're really doing, i. e.:

You write "add <something>", but your patch is actually exchanging one
<somthing> with another <something>.

The reader of the commit message would probably like to know why you're
doing that. Partially copying the original Linux kernel commit message
should be ok.

Also, given that changes a string, does it qualify for a "Fixes:" tag?


Thanks,
Corinna


On Aug 30 22:10, Brian Inglis wrote:
> Signed-off-by: Brian Inglis <Brian.Inglis@Shaw.ca>
> ---
>  winsup/cygwin/fhandler/proc.cc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/winsup/cygwin/fhandler/proc.cc b/winsup/cygwin/fhandler/proc.cc
> index cbc49a12a417..be107cb8eacc 100644
> --- a/winsup/cygwin/fhandler/proc.cc
> +++ b/winsup/cygwin/fhandler/proc.cc
> @@ -1652,7 +1652,7 @@ format_proc_cpuinfo (void *, char *&destbuf)
>  /*	  ftcprint (features2, 11, "sev_64b");*//* SEV 64 bit host guest only */
>  /*	  ftcprint (features2, 12, "sev_rest_inj");   *//* SEV restricted injection */
>  /*	  ftcprint (features2, 13, "sev_alt_inj");    *//* SEV alternate injection */
> -/*	  ftcprint (features2, 14, "sev_es_dbg_swap");*//* SEV-ES debug state swap */
> +	  ftcprint (features2, 14, "debug_swap");   /* SEV-ES full debug state swap */
>  /*	  ftcprint (features2, 15, "no_host_ibs");    *//* host IBS unsupported */
>  /*	  ftcprint (features2, 16, "vte");    *//* virtual transparent encryption */
>  	}
> -- 
> 2.39.0

  reply	other threads:[~2023-08-31  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  4:10 Brian Inglis
2023-08-31  9:08 ` Corinna Vinschen [this message]
2023-08-31 20:12   ` Brian Inglis

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=ZPBYc2ut2HAIWZCw@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-patches@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).