From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nilesh Javali <njavali@marvell.com>,
GR-QLogic-Storage-Upstream@marvell.com,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Himanshu Madhani <himanshu.madhani@oracle.com>
Subject: Re: [PATCH v5 1/4] scsi: qla2xxx: Remove unused del_sess_list field
Date: Thu, 1 Sep 2022 01:12:52 -0400 [thread overview]
Message-ID: <166200877450.26143.13114640534200573694.b4-ty@oracle.com> (raw)
In-Reply-To: <0c335e86-5624-b599-5137-f1377419fb0c@I-love.SAKURA.ne.jp>
On Sun, 21 Aug 2022 12:57:50 +0900, Tetsuo Handa wrote:
> "struct qla_tgt"->del_sess_list is no longer used since commit
> 726b85487067d7f5 ("qla2xxx: Add framework for async fabric discovery").
>
>
Applied to 6.1/scsi-queue, thanks!
[1/4] scsi: qla2xxx: Remove unused del_sess_list field
https://git.kernel.org/mkp/scsi/c/e6852b41b560
[2/4] scsi: qla2xxx: Remove unused qlt_tmr_work()
https://git.kernel.org/mkp/scsi/c/1b2b8d45ccd6
[3/4] scsi: qla2xxx: always wait for qlt_sess_work_fn() from qlt_stop_phase1()
https://git.kernel.org/mkp/scsi/c/a4345557527f
[4/4] scsi: qla2xxx: avoid flush_scheduled_work() usage
https://git.kernel.org/mkp/scsi/c/3cb0643a9aae
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-09-01 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 3:57 [PATCH v5 1/4] scsi: qla2xxx: Remove unused del_sess_list field Tetsuo Handa
2022-08-21 3:58 ` [PATCH v5 2/4] scsi: qla2xxx: Remove unused qlt_tmr_work() Tetsuo Handa
2022-08-21 3:59 ` [PATCH v5 3/4] scsi: qla2xxx: always wait for qlt_sess_work_fn() from qlt_stop_phase1() Tetsuo Handa
2022-08-21 3:59 ` [PATCH v5 4/4] scsi: qla2xxx: avoid flush_scheduled_work() usage Tetsuo Handa
2022-08-23 3:54 ` [PATCH v5 1/4] scsi: qla2xxx: Remove unused del_sess_list field Martin K. Petersen
2022-09-01 5:12 ` 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=166200877450.26143.13114640534200573694.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=himanshu.madhani@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=njavali@marvell.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).