From: Ingo Molnar <mingo@kernel.org>
To: David Windsor <dwindsor@gmail.com>
Cc: peterz@infradead.org, elena.reshetova@intel.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>
Subject: [kernel-hardening] Re: [PATCH] refcount: add refcount_t API kernel-doc comments
Date: Fri, 10 Mar 2017 08:25:07 +0100 [thread overview]
Message-ID: <20170310072507.GB4909@gmail.com> (raw)
In-Reply-To: <1488506159-3506-1-git-send-email-dwindsor@gmail.com>
* David Windsor <dwindsor@gmail.com> wrote:
> This adds kernel-doc comments for the new refcount_t API.
>
> v2: incorporate fixes from Peter Zijlstra and Ingo Molnar
>
> Signed-off-by: David Windsor <dwindsor@gmail.com>
> ---
> lib/refcount.c | 122 +++++++++++++++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 110 insertions(+), 12 deletions(-)
Patch does not apply cleanly anymore, could you please merge it to Linus's latest
and resend?
Thanks!
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: David Windsor <dwindsor@gmail.com>
Cc: peterz@infradead.org, elena.reshetova@intel.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] refcount: add refcount_t API kernel-doc comments
Date: Fri, 10 Mar 2017 08:25:07 +0100 [thread overview]
Message-ID: <20170310072507.GB4909@gmail.com> (raw)
In-Reply-To: <1488506159-3506-1-git-send-email-dwindsor@gmail.com>
* David Windsor <dwindsor@gmail.com> wrote:
> This adds kernel-doc comments for the new refcount_t API.
>
> v2: incorporate fixes from Peter Zijlstra and Ingo Molnar
>
> Signed-off-by: David Windsor <dwindsor@gmail.com>
> ---
> lib/refcount.c | 122 +++++++++++++++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 110 insertions(+), 12 deletions(-)
Patch does not apply cleanly anymore, could you please merge it to Linus's latest
and resend?
Thanks!
Ingo
next prev parent reply other threads:[~2017-03-10 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 1:55 [kernel-hardening] [PATCH] refcount: add refcount_t API kernel-doc comments David Windsor
2017-03-03 1:55 ` David Windsor
2017-03-09 22:58 ` [kernel-hardening] " Kees Cook
2017-03-10 7:25 ` Ingo Molnar [this message]
2017-03-10 7:25 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2017-03-01 3:34 [kernel-hardening] " David Windsor
2017-03-01 7:38 ` [kernel-hardening] " Ingo Molnar
2017-03-01 8:47 ` Peter Zijlstra
2017-02-07 23:56 [kernel-hardening] " David Windsor
2017-02-08 0:49 ` [kernel-hardening] " Kees Cook
2017-02-10 14:44 ` David Windsor
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=20170310072507.GB4909@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 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.