public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: David Windsor <dwindsor@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Reshetova, Elena" <elena.reshetova@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH v3] refcount: add refcount_t API kernel-doc comments
Date: Thu, 23 Mar 2017 08:40:01 +0100	[thread overview]
Message-ID: <20170323074001.GB14258@gmail.com> (raw)
In-Reply-To: <CAGXu5jJuzpSeosAQxkewWB3804+pUrJ9HiU3p-8SOo2hTwFwbQ@mail.gmail.com>


* Kees Cook <keescook@chromium.org> wrote:

> On Fri, Mar 10, 2017 at 7:34 AM, David Windsor <dwindsor@gmail.com> wrote:
> > v3: rebase against latest Linus tree; re-add include/linux/refcount.h
> > missing from v2 series
> >
> > Signed-off-by: David Windsor <dwindsor@gmail.com>
> 
> Reviewed-by: Kees Cook <keescook@chromium.org>
> 
> Ingo, can you pull this into tip? I like having more documentation here. :)

So I hopped into my time machine and applied it to tip:locking/core as of March 
13th:

  commit bd174169c7a12a37b3b4aa2221f084ade010b182
  Author:     David Windsor <dwindsor@gmail.com>
  AuthorDate: Fri Mar 10 10:34:12 2017 -0500
  Commit:     Ingo Molnar <mingo@kernel.org>
  CommitDate: Mon Mar 13 07:41:08 2017 +0100

You are welcome! ;-)

Thanks,

	Ingo

  reply	other threads:[~2017-03-23  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 15:34 [PATCH v3] refcount: add refcount_t API kernel-doc comments David Windsor
2017-03-13  6:46 ` [tip:locking/core] locking/refcount: Add " tip-bot for David Windsor
2017-03-22 19:32 ` [PATCH v3] refcount: add " Kees Cook
2017-03-23  7:40   ` Ingo Molnar [this message]
2017-03-23 14:06     ` Kees Cook

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=20170323074001.GB14258@gmail.com \
    --to=mingo@kernel.org \
    --cc=dwindsor@gmail.com \
    --cc=elena.reshetova@intel.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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