public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>
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>,
	Qiheng Lin <linqiheng@huawei.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH 0/2] s390/dasd: patches
Date: Thu, 09 Feb 2023 17:05:56 -0700	[thread overview]
Message-ID: <167598755656.7194.16272906680345697326.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230210000253.1644903-1-sth@linux.ibm.com>


On Fri, 10 Feb 2023 01:02:51 +0100, Stefan Haberland wrote:
> 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
> 
> [...]

Applied, thanks!

[1/2] s390/dasd: sort out physical vs virtual pointers usage
      commit: b87c52e431adfe2dfe8634216b317b4a952aa9fc
[2/2] s390/dasd: Fix potential memleak in dasd_eckd_init()
      commit: 460e9bed82e49db1b823dcb4e421783854d86c40

Best regards,
-- 
Jens Axboe




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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  0:02 [PATCH 0/2] s390/dasd: patches Stefan Haberland
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 ` Jens Axboe [this message]
  -- 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=167598755656.7194.16272906680345697326.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=borntraeger@linux.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 \
    --cc=sth@linux.ibm.com \
    /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