From: "Martin K. Petersen (Oracle)" <mkp@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Brian King <brking@us.ibm.com>, Hannes Reinecke <hare@suse.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Matthew Wilcox <willy@infradead.org>,
Wen Xiong <wenxiong@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
Hannes Reinecke <hare@kernel.org>,
John Garry <john.g.garry@oracle.com>
Subject: Re: [PATCH v2 0/4] scsi: replace __get_free_pages() with kmalloc()
Date: Tue, 01 Sep 2026 22:42:39 -0400 [thread overview]
Message-ID: <yq1se3sfk71.fsf@mail.kernel.org> (raw)
In-Reply-To: <apK13danJIU2PD8f@kernel.org> (Mike Rapoport's message of "Sat, 29 Aug 2026 13:35:09 +0300")
Mike,
> This seems to fall between the cracks.
>
> Do you want me to resend?
It still applies. Now queued up, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-09-02 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 6:13 [PATCH v2 0/4] scsi: replace __get_free_pages() with kmalloc() Mike Rapoport (Microsoft)
2026-07-04 6:13 ` [PATCH v2 1/4] scsi: target: file: use kmalloc() to allocate temporary protection buffer Mike Rapoport (Microsoft)
2026-07-04 6:13 ` [PATCH v2 2/4] scsi: proc: use kmalloc() in proc writers Mike Rapoport (Microsoft)
2026-07-04 6:13 ` [PATCH v2 3/4] scsi: ipr: use kmalloc() to allocate IPR dump buffer memory Mike Rapoport (Microsoft)
2026-07-04 6:28 ` sashiko-bot
2026-07-04 6:13 ` [PATCH v2 4/4] scsi: sym53c8xx_2: replace __get_free_pages() with kmalloc() Mike Rapoport (Microsoft)
2026-07-04 6:22 ` sashiko-bot
2026-07-20 12:43 ` [PATCH v2 0/4] scsi: " Mike Rapoport
2026-08-29 10:35 ` Mike Rapoport
2026-09-02 2:42 ` Martin K. Petersen (Oracle) [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=yq1se3sfk71.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=brking@us.ibm.com \
--cc=hare@kernel.org \
--cc=hare@suse.com \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rppt@kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=wenxiong@linux.ibm.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox