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] several fixes
Date: Wed, 10 Apr 2019 00:12:03 +0100	[thread overview]
Message-ID: <20190409231203.GP2217@ZenIV.linux.org.uk> (raw)

	A few regression fixes from this cycle

The following changes since commit 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539:

  Merge branch 'work.aio' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2019-04-01 08:28:36 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes

for you to fetch changes up to 6af1c849dfb1f1d326fbdd157c9bc882b921f450:

  aio: use kmem_cache_free() instead of kfree() (2019-04-04 20:13:59 -0400)

----------------------------------------------------------------
Dan Carpenter (1):
      aio: Fix an error code in __io_submit_one()

Wei Yongjun (1):
      aio: use kmem_cache_free() instead of kfree()

YueHaibing (1):
      iov_iter: Fix build error without CONFIG_CRYPTO

 fs/aio.c       | 4 ++--
 lib/iov_iter.c | 4 ++++
 2 files changed, 6 insertions(+), 2 deletions(-)

             reply	other threads:[~2019-04-09 23:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 23:12 Al Viro [this message]
2019-04-10  2:30 ` [git pull] several fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2014-09-07 17:35 Al Viro
2011-03-16 14:42 Al Viro
2011-03-16 17:17 ` Miklos Szeredi
2011-03-16 17:42   ` Linus Torvalds
2011-03-16 18:17     ` Miklos Szeredi
2011-03-16 18:49       ` Linus Torvalds
2011-03-16 20:21         ` Al Viro
2011-03-16 20:29           ` Linus Torvalds
2011-03-16 19:51   ` 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=20190409231203.GP2217@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