mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Nicolai Stange <nicstange@gmail.com>
Subject: [PATCH 0/2] debugfs: fixup to file removal protection series
Date: Sun,  6 Mar 2016 20:59:03 +0100	[thread overview]
Message-ID: <1457294345-4588-1-git-send-email-nicstange@gmail.com> (raw)

Version v4 of the series ("fix debugfs file removal races")
to be found at http://lkml.kernel.org/g/8737sjo7qa.fsf@gmail.com
has been applied to the driver-core tree's driver-core-testing branch.

Unfortunately, the kbuild test robot discovered two minor issues.

To fix these, there are two options. The first one is to replace the
v4 version of the aforementioned series with v5 available at
http://lkml.kernel.org/g/1457267103-28910-1-git-send-email-nicstange@gmail.com

The other, rebaseless option is to apply the two fixup patches
contained within this series.

Both ways lead to identical code in the end.

This series is applicable to the the driver-core tree's
driver-core-testing branch. 

Nicolai Stange (2):
  debugfs: fix DocBook comment of debugfs_use_file_start()
  debugfs: inline dummy implementations of
    debugfs_use_file_start()/_finish()

 fs/debugfs/file.c       | 2 +-
 include/linux/debugfs.h | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

-- 
2.7.2

             reply	other threads:[~2016-03-06 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 19:59 Nicolai Stange [this message]
2016-03-06 19:59 ` [PATCH 1/2] debugfs: fix DocBook comment of debugfs_use_file_start() Nicolai Stange
2016-03-06 19:59 ` [PATCH 2/2] debugfs: inline dummy implementations of debugfs_use_file_start()/_finish() Nicolai Stange
2016-03-22 13:17 ` [PATCH 0/2] debugfs: fixup to file removal protection series 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=1457294345-4588-1-git-send-email-nicstange@gmail.com \
    --to=nicstange@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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

Powered by JetHome