From: John Garry <john.g.garry@oracle.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>, liuqiangneo@163.com
Cc: James.Bottomley@HansenPartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Qiang Liu <liuqiang@kylinos.cn>
Subject: Re: [PATCH] scsi: aic94xx: remove self-assigned redundant code
Date: Wed, 20 Aug 2025 10:24:10 +0100 [thread overview]
Message-ID: <0a345fc9-e780-486c-8724-2c313343cc51@oracle.com> (raw)
In-Reply-To: <yq1h5y2vh09.fsf@ca-mkp.ca.oracle.com>
On 20/08/2025 04:08, Martin K. Petersen wrote:
>
>> Assigning ssp_task.retry_count to itself has no effect
>
>> scb->ssp_task.data_dir = data_dir_flags[task->data_dir];
>> - scb->ssp_task.retry_count = scb->ssp_task.retry_count;
>
> This begs the question of what the original author intended to write.
>
If you check commit 86344494e364, I got rid off sas_task.retry_count as
it was never used. This means that we explicitly set
scb->ata_task.retry_count to zero now.
I guess that they wanted to something like that for scb->ssp_task, but
there was no sas_task member to copy from.
The value in scb->ssp_task.retry_count would be zero from
asd_ascb_alloc() -> asd_init_ascb(). So dropping this self-assigned code
should be ok. However, it would be nice to have consistent code for all
protocol frame types, so we could get rid of setting
scb->ata_task.retry_count = 0 also.
next prev parent reply other threads:[~2025-08-20 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 2:30 liuqiangneo
2025-08-20 3:08 ` Martin K. Petersen
2025-08-20 9:24 ` John Garry [this message]
2025-08-25 15:59 ` Martin K. Petersen
2025-08-31 2:11 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 2:29 liuqiangneo
2025-08-19 2:28 liuqiangneo
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=0a345fc9-e780-486c-8724-2c313343cc51@oracle.com \
--to=john.g.garry@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liuqiang@kylinos.cn \
--cc=liuqiangneo@163.com \
--cc=martin.petersen@oracle.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®