From: Hannes Reinecke <hare@suse.de>
To: Chandrakanth Patil <chandrakanth.patil@broadcom.com>,
linux-scsi@vger.kernel.org
Cc: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
kiran-kumar.kasturi@broadcom.com, sankar.patra@broadcom.com,
sasikumar.pc@broadcom.com,
shivasharan.srikanteshwara@broadcom.com,
anand.lodnoor@broadcom.com
Subject: Re: [PATCH 2/5] megaraid_sas: Remove IO buffer hole detection logic
Date: Wed, 13 May 2020 08:21:00 +0200 [thread overview]
Message-ID: <804ec0d0-b403-4e23-1946-415f4d9c9c3a@suse.de> (raw)
In-Reply-To: <20200508083838.22778-3-chandrakanth.patil@broadcom.com>
On 5/8/20 10:38 AM, Chandrakanth Patil wrote:
> As blk_queue_virt_boundary() API in slave_configure ensures that no IOs
> will come with holes/gaps. Hence, code logic to detect the holes/gaps in
> IO buffer is not required.
>
> Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
> Signed-off-by: Chandrakanth Patil <chandrakanth.patil@broadcom.com>
> ---
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 58 -----------------------------
> 1 file changed, 58 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2020-05-13 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 8:38 [PATCH 0/5] megaraid_sas: driver updates for 07.714.04.00-rc1 Chandrakanth Patil
2020-05-08 8:38 ` [PATCH 1/5] megaraid_sas: Limit device qd to controller qd when device qd is greater than controller qd Chandrakanth Patil
2020-05-13 6:20 ` Hannes Reinecke
2020-05-08 8:38 ` [PATCH 2/5] megaraid_sas: Remove IO buffer hole detection logic Chandrakanth Patil
2020-05-13 6:21 ` Hannes Reinecke [this message]
2020-05-12 3:48 ` [PATCH 0/5] megaraid_sas: driver updates for 07.714.04.00-rc1 Martin K. Petersen
2020-05-13 21:38 ` Chandrakanth Patil
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=804ec0d0-b403-4e23-1946-415f4d9c9c3a@suse.de \
--to=hare@suse.de \
--cc=anand.lodnoor@broadcom.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=kiran-kumar.kasturi@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sankar.patra@broadcom.com \
--cc=sasikumar.pc@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.