All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 5.18-rc6
Date: Fri, 6 May 2022 20:10:57 -0600	[thread overview]
Message-ID: <c9ef8d83-8f8e-0b03-b197-bd6d6105059a@kernel.dk> (raw)

Hi Linus,

Single revert for a change that isn't needed in 5.18, and a small series
for s390/dasd. Please pull!


The following changes since commit 09df6a75fffa68169c5ef9bef990cd7ba94f3eef:

  bfq: Fix warning in bfqq_request_over_limit() (2022-04-29 06:45:37 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/block-5.18-2022-05-06

for you to fetch changes up to f1c8781ac9d87650ccf45a354c0bbfa3f9230371:

  s390/dasd: Use kzalloc instead of kmalloc/memset (2022-05-05 20:08:27 -0600)

----------------------------------------------------------------
block-5.18-2022-05-06

----------------------------------------------------------------
Haowen Bai (1):
      s390/dasd: Use kzalloc instead of kmalloc/memset

Jan Höppner (2):
      s390/dasd: Fix read for ESE with blksize < 4k
      s390/dasd: Fix read inconsistency for ESE DASD devices

Ming Lei (1):
      Revert "block: release rq qos structures for queue without disk"

Stefan Haberland (2):
      s390/dasd: fix data corruption for ESE devices
      s390/dasd: prevent double format of tracks for ESE devices

 block/blk-core.c               |  4 ----
 drivers/s390/block/dasd.c      | 18 +++++++++++++++---
 drivers/s390/block/dasd_eckd.c | 33 ++++++++++++++++++++++-----------
 drivers/s390/block/dasd_int.h  | 14 ++++++++++++++
 4 files changed, 51 insertions(+), 18 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2022-05-07  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07  2:10 Jens Axboe [this message]
2022-05-07 18:11 ` [GIT PULL] Block fixes for 5.18-rc6 pr-tracker-bot

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=c9ef8d83-8f8e-0b03-b197-bd6d6105059a@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@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.