From: Oleg Nesterov <oleg@redhat.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"acme@kernel.org" <acme@kernel.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] uprobes: convert uprobe.ref to refcount_t
Date: Thu, 31 Jan 2019 18:34:14 +0100 [thread overview]
Message-ID: <20190131173414.GA5402@redhat.com> (raw)
In-Reply-To: <2236FBA76BA1254E88B949DDB74E612BA4B9BCAD@IRSMSX102.ger.corp.intel.com>
On 01/31, Reshetova, Elena wrote:
>
> > [ Cc'ing Masami as he maintains uprobes (we need to add uprobes to
> > > the MAINTAINERS file ]
> >
> > Thanks Steve, I think it is maintained mainly by Srikar and Oleg.
> > Srikar, Oleg, could you update MAINTAINERS file to add UPROBES entry?
> > And ack this change?
>
> Srikar, Oleg, could you please take a look on the change, if possible, it is
> really a trivial one in this case.
this one https://lore.kernel.org/lkml/1547637627-29526-1-git-send-email-elena.reshetova@intel.com/
I guess...
Yes, looks obviously correct, feel free to add my ACK,
Oleg.
next prev parent reply other threads:[~2019-01-31 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 11:20 [PATCH] uprobes: convert uprobe.ref to refcount_t Elena Reshetova
2019-01-16 13:44 ` Steven Rostedt
2019-01-21 3:57 ` Masami Hiramatsu
2019-01-31 10:12 ` Reshetova, Elena
2019-01-31 17:34 ` Oleg Nesterov [this message]
2019-02-01 17:21 ` Srikar Dronamraju
2019-02-04 6:50 ` Reshetova, Elena
2019-02-11 20:21 ` Kees Cook
2019-02-11 20:27 ` Steven Rostedt
2019-02-11 20:28 ` Steven Rostedt
2019-02-11 21:49 ` Kees Cook
2019-02-11 22:10 ` Steven Rostedt
2019-02-12 8:38 ` Reshetova, Elena
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=20190131173414.GA5402@redhat.com \
--to=oleg@redhat.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=elena.reshetova@intel.com \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.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