From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH v4 0/8] fix debugfs file removal races
Date: Sat, 5 Mar 2016 13:26:13 -0800 [thread overview]
Message-ID: <20160305212613.GA29738@kroah.com> (raw)
In-Reply-To: <8737sjo7qa.fsf@gmail.com>
On Tue, Feb 23, 2016 at 02:51:25PM +0100, Nicolai Stange wrote:
> The changes from v3 to v4 are style changes regarding the Coccinelle
> part only -- it has been split off from former [3/7] into its own
> patch [4/8].
>
> The big step has been from v2 to v3 and these changes haven't got any
> review yet.
Well, given that they look sane to me, I've applied them to my tree,
let's see what breaks in linux-next now :)
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-05 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 13:51 [Cocci] [PATCH v4 0/8] fix debugfs file removal races Nicolai Stange
2016-02-23 13:52 ` [Cocci] [PATCH v4 1/8] debugfs: prevent access to possibly dead file_operations at file open Nicolai Stange
2016-02-23 13:54 ` [Cocci] [PATCH v4 2/8] debugfs: prevent access to removed files' private data Nicolai Stange
2016-02-23 13:55 ` [Cocci] [PATCH v4 3/8] debugfs: add support for self-protecting attribute file fops Nicolai Stange
2016-02-23 13:56 ` [Cocci] [PATCH v4 4/8] debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage Nicolai Stange
2016-02-23 13:57 ` [Cocci] [PATCH v4 5/8] debugfs: unproxify integer attribute files Nicolai Stange
2016-02-23 13:59 ` [Cocci] [PATCH v4 6/8] debugfs: unproxify files created through debugfs_create_bool() Nicolai Stange
2016-02-23 14:00 ` [Cocci] [PATCH v4 7/8] debugfs: unproxify files created through debugfs_create_blob() Nicolai Stange
2016-02-23 14:02 ` [Cocci] [PATCH v4 8/8] debugfs: unproxify files created through debugfs_create_u32_array() Nicolai Stange
2016-03-05 21:26 ` Greg Kroah-Hartman [this message]
2016-03-06 12:54 ` [Cocci] [PATCH v4 0/8] fix debugfs file removal races Nicolai Stange
2016-03-06 13:54 ` Greg Kroah-Hartman
2016-03-06 20:03 ` Nicolai Stange
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=20160305212613.GA29738@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cocci@systeme.lip6.fr \
/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