linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] more ->lookup() cleanups
Date: Thu, 25 Oct 2018 01:18:57 +0100	[thread overview]
Message-ID: <20181025001857.GD32577@ZenIV.linux.org.uk> (raw)

	Some ->lookup() instances are still overcomplicating the life
for themselves, open-coding the stuff that would be handled by
d_splice_alias() just fine.  Simplify a couple of such cases caught
this cycle and document d_splice_alias() intended use.

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.lookup

for you to fetch changes up to 1a16dbaf798c5b68ac767444eb045e6f3adaa16d:

  Document d_splice_alias() calling conventions for ->lookup() users. (2018-10-10 16:52:37 -0400)

----------------------------------------------------------------
Al Viro (3):
      clean erofs_lookup()
      simplify btrfs_lookup()
      Document d_splice_alias() calling conventions for ->lookup() users.

 Documentation/filesystems/porting | 11 +++++++++++
 drivers/staging/erofs/namei.c     | 19 +++++++------------
 fs/btrfs/inode.c                  | 12 +++---------
 3 files changed, 21 insertions(+), 21 deletions(-)

             reply	other threads:[~2018-10-25  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  0:18 Al Viro [this message]
2018-10-25 19:57 ` [git pull] more ->lookup() cleanups Linus Torvalds

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=20181025001857.GD32577@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).