From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] assorted fixes
Date: Sun, 3 Sep 2017 18:15:11 +0100 [thread overview]
Message-ID: <20170903171510.GT5426@ZenIV.linux.org.uk> (raw)
Loose ends and regressions from the last merge window.
Strictly speaking, only binfmt_flat thing is a build regression
per se - the rest is "only sparse cares about that" stuff.
The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98:
Linux 4.13-rc7 (2017-08-27 17:20:40 -0700)
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 b38e51cd167927225ae0c26bd404403b7b1cd2f3:
binfmt_flat: fix arch/m32r and arch/microblaze flat_put_addr_at_rp() (2017-08-31 17:32:42 -0400)
----------------------------------------------------------------
Al Viro (1):
teach SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE to handle __bitwise arguments
Bart Van Assche (2):
<linux/uaccess.h>: Fix copy_in_user() declaration
compat_hdio_ioctl: Fix a declaration
Christoph Hellwig (1):
annotate RWF_... flags
Randy Dunlap (1):
binfmt_flat: fix arch/m32r and arch/microblaze flat_put_addr_at_rp()
arch/m32r/include/asm/flat.h | 3 ++-
arch/microblaze/include/asm/flat.h | 2 +-
arch/s390/include/asm/compat.h | 5 ++--
block/compat_ioctl.c | 2 +-
fs/nfsd/vfs.c | 2 +-
fs/read_write.c | 50 +++++++++++++++++++-------------------
include/linux/compat.h | 18 +++++++++++---
include/linux/fs.h | 12 +++++----
include/linux/syscalls.h | 13 +++++-----
include/linux/uaccess.h | 2 +-
include/uapi/linux/aio_abi.h | 21 ++++++++--------
include/uapi/linux/fs.h | 28 +++++++++++++++------
12 files changed, 94 insertions(+), 64 deletions(-)
next reply other threads:[~2017-09-03 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 17:15 Al Viro [this message]
2017-09-03 18:12 ` [git pull] assorted fixes Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2013-05-31 20:24 Al Viro
2011-08-01 18:16 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=20170903171510.GT5426@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.