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-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] vfs.git - aio ioprio
Date: Fri, 8 Jun 2018 06:27:45 +0100	[thread overview]
Message-ID: <20180608052745.GZ30522@ZenIV.linux.org.uk> (raw)

	The rest of aio stuff for this cycle - Adam's aio ioprio series

The following changes since commit 1da92779e2e8f309d5aecbbed346e7f812b174e8:

  aio: sanitize the limit checking in io_submit(2) (2018-05-29 23:20:17 -0400)

are available in the git repository at:

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

for you to fetch changes up to 9a6d9a62e0fd4b9927c3124db0f25fc6b4fb6576:

  fs: aio ioprio use ioprio_check_cap ret val (2018-06-04 14:20:39 -0400)

----------------------------------------------------------------
Adam Manzanares (7):
      block: add ioprio_check_cap function
      fs: Convert kiocb rw_hint from enum to u16
      fs: Add aio iopriority support
      fs: blkdev set bio prio from kiocb prio
      fs: iomap dio set bio prio from kiocb prio
      fs: aio ioprio add explicit block layer dependence
      fs: aio ioprio use ioprio_check_cap ret val

 block/ioprio.c               | 22 ++++++++++++++++------
 drivers/block/loop.c         |  3 +++
 fs/aio.c                     | 18 +++++++++++++++++-
 fs/block_dev.c               |  2 ++
 fs/iomap.c                   |  1 +
 include/linux/fs.h           | 16 ++++++++++++++--
 include/linux/ioprio.h       |  9 +++++++++
 include/uapi/linux/aio_abi.h |  1 +
 8 files changed, 63 insertions(+), 9 deletions(-)

                 reply	other threads:[~2018-06-08  5:27 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=20180608052745.GZ30522@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