mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Tobin C. Harding" <me@tobin.cc>, Petr Mladek <pmladek@suse.com>,
	Joe Perches <joe@perches.com>, Ian Campbell <ijc@hellion.org.uk>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	kernel-hardening@lists.openwall.com,
	linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	William Roberts <william.c.roberts@intel.com>,
	Chris Fries <cfries@google.com>,
	Dave Weinstein <olorin@google.com>
Subject: Re: [kernel-hardening] [RFC V2 0/6] add more kernel pointer filter options
Date: Wed, 4 Oct 2017 09:28:15 -0400	[thread overview]
Message-ID: <20171004092815.71b6243c@gandalf.local.home> (raw)
In-Reply-To: <20171004124233.GA19372@kroah.com>

On Wed, 4 Oct 2017 14:42:33 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> > Is correct protocol for me to add your Signed-off-by tag to each patch from this RFC? Or is the
> > protocol for you to add the tag yourself when the real version is posted?   
> 
> You can add my signed-off-by to your new patches,

I was always told that one should never add someone else's
signed-off-by, because that's not what it means. 

I was told that this would be an Acked-by or Reviewed-by.

>From Documentation/process/submitting-patches.rst:

====
12) When to use Acked-by: and Cc:
---------------------------------

The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery path.

If a person was not directly involved in the preparation or handling of a
patch but wishes to signify and record their approval of it then they can
ask to have an Acked-by: line added to the patch's changelog.

Acked-by: is often used by the maintainer of the affected code when that
maintainer neither contributed to nor forwarded the patch.

Acked-by: is not as formal as Signed-off-by:.  It is a record that the acker
has at least reviewed the patch and has indicated acceptance.  Hence patch
mergers will sometimes manually convert an acker's "yep, looks good to me"
into an Acked-by: (but note that it is usually better to ask for an
explicit ack).
====

-- Steve

  reply	other threads:[~2017-10-04 13:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01  0:06 Tobin C. Harding
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 1/6] lib: vsprintf: additional kernel pointer filtering options Tobin C. Harding
2017-10-04  8:55   ` Greg KH
2017-10-04 13:08     ` Steven Rostedt
2017-10-04 13:26       ` Greg KH
2017-10-04 13:29         ` Steven Rostedt
2017-10-04 13:54           ` Greg KH
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 2/6] lib: vsprintf: whitelist stack traces Tobin C. Harding
2017-10-02 10:42   ` Will Deacon
2017-10-02 21:49     ` Tobin C. Harding
2017-10-04  8:56     ` Greg KH
2017-10-04  8:58       ` Will Deacon
2017-10-04  9:02         ` Greg KH
2017-10-04 10:42           ` Tobin C. Harding
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 3/6] lib: vsprintf: physical address kernel pointer filtering options Tobin C. Harding
2017-10-04  8:58   ` Greg KH
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 4/6] lib: vsprintf: default kptr_restrict to the maximum value Tobin C. Harding
2017-10-04  8:55   ` Greg KH
2017-10-04 16:42   ` Kees Cook
2017-10-04 16:48     ` Roberts, William C
2017-10-04 17:08     ` Linus Torvalds
2017-10-04 17:28       ` Linus Torvalds
2017-10-04 19:13         ` Jann Horn
2017-10-04 19:23           ` Linus Torvalds
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 5/6] lib: vsprintf: add "%paP", "%papP", and "%padP" specifiers Tobin C. Harding
2017-10-04  8:58   ` Greg KH
2017-10-01  0:06 ` [kernel-hardening] [RFC V2 6/6] drivers: uio: un-restrict sysfs pointers for UIO Tobin C. Harding
2017-10-04  8:58   ` Greg KH
2017-10-01  0:11 ` [kernel-hardening] [RFC V2 0/6] add more kernel pointer filter options Tobin C. Harding
2017-10-04  8:57   ` Greg KH
2017-10-04 10:45     ` Tobin C. Harding
2017-10-04  8:58 ` Greg KH
2017-10-04 10:50   ` Tobin C. Harding
2017-10-04 12:42     ` Greg KH
2017-10-04 13:28       ` Steven Rostedt [this message]
2017-10-04 13:31         ` Steven Rostedt
2017-10-04 16:17   ` Roberts, William C
2017-10-04 15:41 ` Linus Torvalds
2017-10-04 16:22   ` Boris Lukashev
2017-10-04 16:29     ` Linus Torvalds
2017-10-04 16:54       ` Steven Rostedt
2017-10-04 16:32 ` Ian Campbell

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=20171004092815.71b6243c@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=catalin.marinas@arm.com \
    --cc=cfries@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc@hellion.org.uk \
    --cc=joe@perches.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=olorin@google.com \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=will.deacon@arm.com \
    --cc=william.c.roberts@intel.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

all inboxes | Powered by JetHome®