From: Dave Hansen <dave@sr71.net>
To: Eric Paris <eparis@redhat.com>
Cc: john@johnmccutchan.com, rlove@rlove.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] inotify: actually check for invalid bits in sys_inotify_add_watch()
Date: Wed, 9 Sep 2015 16:32:37 -0700 [thread overview]
Message-ID: <55F0C195.4000003@sr71.net> (raw)
In-Reply-To: <1441840602.27892.99.camel@redhat.com>
On 09/09/2015 04:16 PM, Eric Paris wrote:
> Looks fine to me. And usually akpm picks them up these days.
Is that an Acked-by? :)
next prev parent reply other threads:[~2015-09-09 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 17:36 [PATCH] inotify: actually check for invalid bits in sys_inotify_add_watch() Dave Hansen
2015-09-09 21:59 ` Dave Hansen
2015-09-09 22:37 ` Josh Boyer
2015-09-09 23:16 ` Eric Paris
2015-09-09 23:32 ` Dave Hansen [this message]
2015-09-10 20:49 ` Andrew Morton
2015-09-21 11:29 ` Andrey Wagin
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=55F0C195.4000003@sr71.net \
--to=dave@sr71.net \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).