All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Haberland <sth@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
	Jan Hoeppner <hoeppner@linux.ibm.com>,
	linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Qiheng Lin <linqiheng@huawei.com>
Subject: [PATCH 0/2] s390/dasd: patches
Date: Fri, 10 Feb 2023 01:02:51 +0100	[thread overview]
Message-ID: <20230210000253.1644903-1-sth@linux.ibm.com> (raw)

Hi Jens,

please apply the following patches for the next merge window that:
 - sort out physical and virtual pointers
 - fix a potential memleak in dasd_eckd_init

Thanks.

Alexander Gordeev (1):
  s390/dasd: sort out physical vs virtual pointers usage

Qiheng Lin (1):
  s390/dasd: Fix potential memleak in dasd_eckd_init()

 drivers/s390/block/dasd.c          |   5 +-
 drivers/s390/block/dasd_3990_erp.c |  10 +--
 drivers/s390/block/dasd_alias.c    |   6 +-
 drivers/s390/block/dasd_eckd.c     | 104 ++++++++++++++---------------
 drivers/s390/block/dasd_eer.c      |   2 +-
 drivers/s390/block/dasd_fba.c      |  14 ++--
 6 files changed, 70 insertions(+), 71 deletions(-)

-- 
2.37.2


             reply	other threads:[~2023-02-10  0:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  0:02 Stefan Haberland [this message]
2023-02-10  0:02 ` [PATCH 1/2] s390/dasd: sort out physical vs virtual pointers usage Stefan Haberland
2023-02-10  0:02 ` [PATCH 2/2] s390/dasd: Fix potential memleak in dasd_eckd_init() Stefan Haberland
2023-02-10  0:05 ` [PATCH 0/2] s390/dasd: patches Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2021-07-01 14:22 [PATCH 0/2] s390/dasd patches Stefan Haberland
2021-07-01 15:27 ` Jens Axboe

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=20230210000253.1644903-1-sth@linux.ibm.com \
    --to=sth@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linqiheng@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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.