public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git misc stuff
Date: Sat, 27 Feb 2021 06:00:29 +0000	[thread overview]
Message-ID: <YDnf/cY4c0uOIcVd@zeniv-ca.linux.org.uk> (raw)

	Assorted stuff pile - no common topic here.
One trivial conflict in Documentation/filesystems/porting.rst  

The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:

  Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)

are available in the git repository at:

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

for you to fetch changes up to 6f24784f00f2b5862b367caeecc5cca22a77faa3:

  whack-a-mole: don't open-code iminor/imajor (2021-02-23 10:25:29 -0500)

----------------------------------------------------------------
Al Viro (3):
      audit_alloc_mark(): don't open-code ERR_CAST()
      9p: fix misuse of sscanf() in v9fs_stat2inode()
      whack-a-mole: don't open-code iminor/imajor

Eric Biggers (2):
      vfs: don't unnecessarily clone write access for writable fds
      fs/inode.c: make inode_init_always() initialize i_ino to 0

 Documentation/filesystems/porting.rst  |  7 +++++
 arch/sh/boards/mach-landisk/gio.c      |  6 ++--
 drivers/block/loop.c                   |  2 +-
 drivers/dax/super.c                    |  2 +-
 drivers/rtc/rtc-m41t80.c               |  4 +--
 drivers/s390/char/vmur.c               |  2 +-
 drivers/staging/vme/devices/vme_user.c | 12 ++++----
 fs/9p/vfs_inode.c                      | 21 ++++++--------
 fs/gfs2/inode.c                        |  4 +--
 fs/inode.c                             |  1 +
 fs/jfs/super.c                         |  1 -
 fs/namespace.c                         | 53 +++++++++++++---------------------
 include/linux/mount.h                  |  1 -
 kernel/audit_fsnotify.c                |  2 +-
 14 files changed, 53 insertions(+), 65 deletions(-)

             reply	other threads:[~2021-02-27  6:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27  6:00 Al Viro [this message]
2021-02-27 16:21 ` [git pull] vfs.git misc stuff Linus Torvalds
2021-02-27 17:18   ` Al Viro
2021-02-27 16:29 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-04-02  1:52 Al Viro
2022-04-02  3:07 ` pr-tracker-bot
2020-12-24 23:35 Al Viro
2020-12-25 19:09 ` pr-tracker-bot
2017-05-09  5:34 Al Viro

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=YDnf/cY4c0uOIcVd@zeniv-ca.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