From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: convert dasd to the atomic queue limits update API v2
Date: Wed, 06 Mar 2024 08:35:18 -0700 [thread overview]
Message-ID: <170973931869.23995.8429422816795215869.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240228133742.806274-1-hch@lst.de>
On Wed, 28 Feb 2024 05:37:39 -0800, Christoph Hellwig wrote:
> this series against the block/for-6.9 tree converts dasd to the new atomic
> queue limits update API. It is compile tested only as I don't have any
> s390 hardware. If this is fine with you it would be great to merge it
> through Jens' tree with your ACKs
>
> Changes since v1:
>
> [...]
Applied, thanks!
[1/3] dasd: cleamup dasd_state_basic_to_ready
commit: 41463f2dfde2824a817789d635be8111cff463f5
[2/3] dasd: move queue setup to common code
commit: 0127a47f58c6bb7b54386960ee66864b937269eb
[3/3] dasd: use the atomic queue limits API
commit: fde07a4d74e3b511105e0b6c9372d42376fbbecb
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-03-06 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 13:37 convert dasd to the atomic queue limits update API v2 Christoph Hellwig
2024-02-28 13:37 ` [PATCH 1/3] dasd: cleamup dasd_state_basic_to_ready Christoph Hellwig
2024-02-28 13:37 ` [PATCH 2/3] dasd: move queue setup to common code Christoph Hellwig
2024-03-06 14:52 ` Stefan Haberland
2024-02-28 13:37 ` [PATCH 3/3] dasd: use the atomic queue limits API Christoph Hellwig
2024-03-06 15:35 ` Jens Axboe [this message]
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=170973931869.23995.8429422816795215869.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@linux.ibm.com \
--cc=svens@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).