mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jason Yan <yanaijie@huawei.com>,
	Wenchao Hao <haowenchao2@huawei.com>,
	John Garry <john.g.garry@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.ibm.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: louhongxiang@huawei.com
Subject: Re: [PATCH] scsi:libsas: Simplify sas_queue_reset and remove unused code
Date: Mon, 31 Jul 2023 11:05:08 +0900	[thread overview]
Message-ID: <7fe583de-966e-1e86-3233-556886c943d1@kernel.org> (raw)
In-Reply-To: <27bb586c-af75-c2da-1b07-02bfb08e5891@huawei.com>

On 7/31/23 10:44, Jason Yan wrote:
> Hi Wenchao,
> 
> On 2023/7/29 18:24, Wenchao Hao wrote:
>> sas_queue_reset is always called with param "wait" set to 0, so
>> remove it from this function's param list. And remove unused
>> function sas_wait_eh.
> 
> I did not find any users passing '1' to sas_queue_reset() in the git 
> history. It seems it is never used. So It's ok to remove it, I guess.
> 
> Just one nit, there should be a blank between "scsi:" and "libsas" in 
> the subject:
> 
> scsi: libsas: Simplify sas_queue_reset and remove unused code
> 
> Otherwise looks good to me:
> Reviewed-by: Jason Yan <yanaijie@huawei.com>

Yeah, code wise, it looks good.
However, I am seeing issues with completions for commands that use command
duration limits. There are some unusual completions that needs special handling
with CDL (e.g. some aborted commands can be notified with a success and
sense-data-available-bit set. For these, we kick libata-EH but it seems that
this is not well working with libsas. So I wonder if this code may need to be
used for CDL... So let's please hold on before applying this. Let me check the
CDL issues I am seeing first.

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2023-07-31  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 10:24 Wenchao Hao
2023-07-31  1:44 ` Jason Yan
2023-07-31  2:05   ` Damien Le Moal [this message]
2023-07-31  2:30     ` Jason Yan
2023-08-15  2:18 ` Damien Le Moal
2023-08-30 12:52 ` haowenchao (C)
2023-08-31  1:25   ` Martin K. Petersen
2023-09-05 10:18 ` Martin K. Petersen

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=7fe583de-966e-1e86-3233-556886c943d1@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=haowenchao2@huawei.com \
    --cc=jejb@linux.ibm.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=louhongxiang@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=yanaijie@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

all inboxes | Powered by JetHome®