From: Davidlohr Bueso <dave@stgolabs.net>
To: Elena Reshetova <elena.reshetova@intel.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
ebiederm@xmission.com, mingo@redhat.com, adobriyan@gmail.com,
serge@hallyn.com, arozansk@redhat.com
Subject: Re: [PATCH 0/3] ipc subsystem refcounter conversions
Date: Wed, 22 Feb 2017 07:41:38 -0800 [thread overview]
Message-ID: <20170222154138.GA5126@linux-80c1.suse> (raw)
In-Reply-To: <1487590189-18151-1-git-send-email-elena.reshetova@intel.com>
On Mon, 20 Feb 2017, Elena Reshetova wrote:
> include/linux/ipc_namespace.h | 5 +++--
> ipc/msgutil.c | 2 +-
> ipc/namespace.c | 4 ++--
> ipc/sem.c | 8 ++++----
> ipc/util.c | 6 +++---
> ipc/util.h | 3 ++-
> 6 files changed, 15 insertions(+), 13 deletions(-)
The SoB list is a bit weird... otherwise, the conversion
obviously makes sense:
Acked-by: Davidlohr Bueso <dave@stgolabs.net>
next prev parent reply other threads:[~2017-02-22 15:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:29 [PATCH 0/3] ipc subsystem refcounter conversions Elena Reshetova
2017-02-20 11:29 ` [PATCH 1/3] ipc: convert ipc_namespace.count from atomic_t to refcount_t Elena Reshetova
2017-05-27 19:41 ` Kees Cook
2017-05-28 12:10 ` Manfred Spraul
2017-02-20 11:29 ` [PATCH 2/3] ipc: convert sem_undo_list.refcnt " Elena Reshetova
2017-05-27 19:44 ` Kees Cook
2017-02-20 11:29 ` [PATCH 3/3] ipc: convert ipc_rcu.refcount " Elena Reshetova
2017-05-27 19:47 ` Kees Cook
2017-02-20 11:42 ` [PATCH 0/3] ipc subsystem refcounter conversions Andy Shevchenko
2017-02-20 12:30 ` Reshetova, Elena
2017-02-22 15:41 ` Davidlohr Bueso [this message]
2017-03-04 0:23 ` Andrew Morton
2017-03-06 9:51 ` Reshetova, Elena
2017-05-27 19:58 ` [kernel-hardening] " Kees Cook
2017-05-27 19:58 ` Kees Cook
2017-05-27 19:58 ` Kees Cook
2017-05-29 8:39 ` [kernel-hardening] " Christoph Hellwig
2017-05-29 8:39 ` Christoph Hellwig
2017-05-29 8:39 ` Christoph Hellwig
2017-05-29 9:11 ` [kernel-hardening] " Eric W. Biederman
2017-05-29 9:11 ` Eric W. Biederman
2017-05-29 9:11 ` Eric W. Biederman
2017-05-29 9:11 ` Eric W. Biederman
2017-05-29 10:24 ` [kernel-hardening] " Peter Zijlstra
2017-05-29 10:24 ` Peter Zijlstra
2017-05-29 10:49 ` [kernel-hardening] " Eric W. Biederman
2017-05-29 10:49 ` Eric W. Biederman
2017-05-29 10:49 ` Eric W. Biederman
2017-05-29 10:49 ` Eric W. Biederman
2017-05-29 11:30 ` [kernel-hardening] " Eric W. Biederman
2017-05-29 11:30 ` Eric W. Biederman
2017-05-29 11:30 ` Eric W. Biederman
2017-05-29 11:30 ` Eric W. Biederman
2017-05-29 11:39 ` [kernel-hardening] " Eric W. Biederman
2017-05-29 11:39 ` Eric W. Biederman
2017-05-29 11:39 ` Eric W. Biederman
2017-05-29 11:39 ` Eric W. Biederman
2017-05-29 12:23 ` [kernel-hardening] " Peter Zijlstra
2017-05-29 12:23 ` Peter Zijlstra
2017-05-29 12:23 ` Peter Zijlstra
2017-05-29 15:43 ` [kernel-hardening] " Peter Zijlstra
2017-05-29 15:43 ` Peter Zijlstra
2017-05-29 15:43 ` Peter Zijlstra
2017-05-29 12:13 ` [kernel-hardening] " Peter Zijlstra
2017-05-29 12:13 ` Peter Zijlstra
2017-05-29 12:13 ` Peter Zijlstra
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=20170222154138.GA5126@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arozansk@redhat.com \
--cc=ebiederm@xmission.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=serge@hallyn.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 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.