From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-scsi@vger.kernel.org, Ye Bin <yebin10@huawei.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
sashal@kernel.org, bvanassche@acm.org
Subject: Re: [PATCH] scsi: Delete unnecessary allocate buffer for every loop when print command
Date: Fri, 24 Jul 2020 22:50:46 -0400 [thread overview]
Message-ID: <159564519423.31464.10229326949845693673.b4-ty@oracle.com> (raw)
In-Reply-To: <20200717090921.29243-2-yebin10@huawei.com>
On Fri, 17 Jul 2020 17:09:21 +0800, Ye Bin wrote:
> We can allocate buffer once, and reuse it. There is unnecessary allocate
> buffer for every loop.
Applied to 5.9/scsi-queue, thanks!
[1/1] scsi: core: Delete unnecessary buffer allocation for every loop iteration
https://git.kernel.org/mkp/scsi/c/811f39479c0c
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-07-25 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:09 [PATCH] scsi: core: Fix "scsi: core: add scsi_host_(block,unblock) helper function" Ye Bin
2020-07-17 9:09 ` [PATCH] scsi: Delete unnecessary allocate buffer for every loop when print command Ye Bin
2020-07-25 2:50 ` Martin K. Petersen [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=159564519423.31464.10229326949845693673.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=yebin10@huawei.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 NNTP newsgroup(s).