From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Vlastimil Babka <vbabka@kernel.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 00/13] s390/cio: replace page allocator calls with k[mz]alloc()
Date: Fri, 18 Sep 2026 18:23:00 +0200 [thread overview]
Message-ID: <bf57f67e-4a51-407a-b869-b9d78a9875b4@linux.ibm.com> (raw)
In-Reply-To: <20260916130613.15587F91-hca@linux.ibm.com>
On 16.09.2026 15:06, Heiko Carstens wrote:
> On Wed, Sep 16, 2026 at 03:03:07PM +0300, Mike Rapoport (Microsoft) wrote:
>> The saga continues :)
>>
>> This series covers CIO, QDIO, SCM and IDAL buffer allocations.
>
> ...
>
>> Mike Rapoport (Microsoft) (13):
>> s390/chsc: Use kzalloc() for CUBs
>> s390/chsc: Use kzalloc() for the SEI work area
>> s390/chsc_sch: Use kzalloc() for CHSC requests
>> s390/chsc_sch: Use __free(kfree) for synchronous CHSC requests
>> s390/cio: Use kzalloc() for CHSC work areas
>> s390/cmf: Use kmalloc() for the CMB area
>> s390/idals: Use kmalloc() for IDAL data buffers
>> s390/qdio_main: Use kzalloc() for the IRQ structure
>> s390/qdio_main: Use kzalloc() for the QDR
>> s390/qdio_setup: Use kzalloc() for QDIO buffers
>> s390/qdio_setup: Use kmalloc() for the storage list
>> s390/qdio_setup: Use kmalloc() for the SSQD request
>> s390/scm: Use kmalloc() for SCM information
>>
>> arch/s390/include/asm/idals.h | 9 +-
>> drivers/s390/cio/chsc.c | 20 +--
>> drivers/s390/cio/chsc_sch.c | 300 ++++++++++++++--------------------------
>> drivers/s390/cio/cmf.c | 11 +-
>> drivers/s390/cio/qdio.h | 2 +-
>> drivers/s390/cio/qdio_main.c | 23 ++-
>> drivers/s390/cio/qdio_setup.c | 14 +-
>> drivers/s390/cio/qdio_thinint.c | 2 +-
>> drivers/s390/cio/scm.c | 7 +-
>> 9 files changed, 150 insertions(+), 238 deletions(-)
>
> As far as I am concerned:
> Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
>
> Waiting for IO folks before applying. Thanks!
Looks good to me! For the full series:
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
--
Peter Oberparleiter
Linux on IBM Z Development - IBM Germany R&D
prev parent reply other threads:[~2026-09-18 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 12:03 Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 01/13] s390/chsc: Use kzalloc() for CUBs Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 02/13] s390/chsc: Use kzalloc() for the SEI work area Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 03/13] s390/chsc_sch: Use kzalloc() for CHSC requests Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 04/13] s390/chsc_sch: Use __free(kfree) for synchronous " Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 05/13] s390/cio: Use kzalloc() for CHSC work areas Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 06/13] s390/cmf: Use kmalloc() for the CMB area Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 07/13] s390/idals: Use kmalloc() for IDAL data buffers Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 08/13] s390/qdio_main: Use kzalloc() for the IRQ structure Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 09/13] s390/qdio_main: Use kzalloc() for the QDR Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 10/13] s390/qdio_setup: Use kzalloc() for QDIO buffers Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 11/13] s390/qdio_setup: Use kmalloc() for the storage list Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 12/13] s390/qdio_setup: Use kmalloc() for the SSQD request Mike Rapoport (Microsoft)
2026-09-16 12:03 ` [PATCH v3 13/13] s390/scm: Use kmalloc() for SCM information Mike Rapoport (Microsoft)
2026-09-16 13:06 ` [PATCH v3 00/13] s390/cio: replace page allocator calls with k[mz]alloc() Heiko Carstens
2026-09-18 16:23 ` Peter Oberparleiter [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=bf57f67e-4a51-407a-b869-b9d78a9875b4@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=svens@linux.ibm.com \
--cc=vbabka@kernel.org \
--cc=vneethv@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
all inboxes | Powered by JetHome®