All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH] scripts: coccinelle: add uses of memzero_explicit
Date: Wed, 10 Dec 2014 22:43:02 +0100	[thread overview]
Message-ID: <5488BE66.8040804@users.sourceforge.net> (raw)
In-Reply-To: <1418242123-8610-1-git-send-email-Julia.Lawall@lip6.fr>

> Memzero_explicit is a version of memset that is resistent to compiler
> optimizations when the set region is about to go out of scope.

Thanks for another interesting update suggestion.


> This was suggested by Daniel Borkmann

How do you think about to amend such a commit message here?

Would it eventually be better to use a tag like "Suggested-by" there
(instead of finishing this sentence with a full stop)?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: cocci@systeme.lip6.fr
Subject: Re: [PATCH] scripts: coccinelle: add uses of memzero_explicit
Date: Wed, 10 Dec 2014 21:43:02 +0000	[thread overview]
Message-ID: <5488BE66.8040804@users.sourceforge.net> (raw)
In-Reply-To: <1418242123-8610-1-git-send-email-Julia.Lawall@lip6.fr>

> Memzero_explicit is a version of memset that is resistent to compiler
> optimizations when the set region is about to go out of scope.

Thanks for another interesting update suggestion.


> This was suggested by Daniel Borkmann

How do you think about to amend such a commit message here?

Would it eventually be better to use a tag like "Suggested-by" there
(instead of finishing this sentence with a full stop)?

Regards,
Markus

  reply	other threads:[~2014-12-10 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 20:08 [Cocci] [PATCH] scripts: coccinelle: add uses of memzero_explicit Julia Lawall
2014-12-10 20:08 ` Julia Lawall
2014-12-10 21:43 ` SF Markus Elfring [this message]
2014-12-10 21:43   ` SF Markus Elfring
2014-12-10 23:18 ` Daniel Borkmann
2014-12-10 23:48 ` Daniel Borkmann

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=5488BE66.8040804@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.lip6.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.