From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git trivial bits
Date: Fri, 4 Jan 2019 19:07:40 +0000 [thread overview]
Message-ID: <20190104190740.GN2217@ZenIV.linux.org.uk> (raw)
A few cleanups + Neil's namespace_unlock() optimization.
It's been in 3 branches (work.misc, misc.misc, work.iov_iter), but
IMO 3 pull requests for the sake of 4 commits unrelated to each
other is over the top...
The following changes since commit 78e1f386170798159a81fdbc5e131836fd808048:
iov_iter: teach csum_and_copy_to_iter() to handle pipe-backed ones (2018-11-25 16:24:49 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
for you to fetch changes up to e4f2283cc6ffefbe414317a0d89b602811b577ac:
Merge branches 'misc.misc' and 'work.iov_iter' into for-linus (2019-01-04 14:02:59 -0500)
----------------------------------------------------------------
Al Viro (3):
iov_iter: reduce code duplication
genheaders: %-<width>s had been there since v6; %-*s - since v7
Merge branches 'misc.misc' and 'work.iov_iter' into for-linus
Chanho Min (1):
exec: make prepare_bprm_creds static
NeilBrown (1):
VFS: use synchronize_rcu_expedited() in namespace_unlock()
fs/exec.c | 2 +-
fs/namespace.c | 2 +-
include/linux/binfmts.h | 1 -
lib/iov_iter.c | 54 ++++++++++++++++-----------------
scripts/selinux/genheaders/genheaders.c | 29 ++++++------------
5 files changed, 38 insertions(+), 50 deletions(-)
reply other threads:[~2019-01-04 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190104190740.GN2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@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).