From: John Garry <john.garry@huawei.com>
To: Kees Cook <keescook@chromium.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Jack Wang <jinpu.wang@profitbricks.com>,
"lindar_liu@usish.com" <lindar_liu@usish.com>,
Jens Axboe <axboe@fb.com>, Hannes Reinecke <hare@suse.com>,
"Johannes Thumshirn" <jthumshirn@suse.de>,
Benjamin Block <bblock@linux.vnet.ibm.com>,
Baoyou Xie <baoyou.xie@linaro.org>,
"weiyongjun (A)" <weiyongjun1@huawei.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH] scsi: sas: Convert timers to use timer_setup()
Date: Tue, 31 Oct 2017 18:13:14 +0000 [thread overview]
Message-ID: <70f0b708-4b73-ee05-96c3-0b45bcba7dd3@huawei.com> (raw)
In-Reply-To: <20171025100800.GA145125@beast>
On 25/10/2017 11:08, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly. This requires adding a pointer to
> hold the timer's target task, as there isn't a link back from slow_task.
>
> Cc: John Garry <john.garry@huawei.com>
> Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: Jack Wang <jinpu.wang@profitbricks.com>
> Cc: lindar_liu@usish.com
> Cc: Jens Axboe <axboe@fb.com>
> Cc: Hannes Reinecke <hare@suse.com>
> Cc: Johannes Thumshirn <jthumshirn@suse.de>
> Cc: Benjamin Block <bblock@linux.vnet.ibm.com>
> Cc: Baoyou Xie <baoyou.xie@linaro.org>
> Cc: Wei Yongjun <weiyongjun1@huawei.com>
> Cc: linux-scsi@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: John Garry <john.garry@huawei.com> #for hisi_sas part
Tested-by: John Garry <john.garry@huawei.com> # basic sanity test for
hisi_sas (+ libsas)
> ---
> drivers/scsi/hisi_sas/hisi_sas.h | 1 -
> drivers/scsi/hisi_sas/hisi_sas_main.c | 14 ++++++--------
> drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 6 +++---
> drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 24 +++++++++++-------------
> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 2 +-
> drivers/scsi/libsas/sas_expander.c | 8 ++++----
> drivers/scsi/libsas/sas_init.c | 3 ++-
> drivers/scsi/libsas/sas_scsi_host.c | 2 +-
> drivers/scsi/mvsas/mv_init.c | 3 +--
> drivers/scsi/mvsas/mv_sas.c | 15 +++++++--------
> drivers/scsi/mvsas/mv_sas.h | 1 -
> drivers/scsi/pm8001/pm8001_sas.c | 11 +++++------
> include/scsi/libsas.h | 1 +
> 13 files changed, 42 insertions(+), 49 deletions(-)
next prev parent reply other threads:[~2017-10-31 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 10:08 [PATCH] scsi: sas: Convert timers to use timer_setup() Kees Cook
2017-10-31 15:56 ` Martin K. Petersen
2017-10-31 18:13 ` John Garry [this message]
2017-11-01 7:58 ` Jinpu Wang
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=70f0b708-4b73-ee05-96c3-0b45bcba7dd3@huawei.com \
--to=john.garry@huawei.com \
--cc=axboe@fb.com \
--cc=baoyou.xie@linaro.org \
--cc=bblock@linux.vnet.ibm.com \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jinpu.wang@profitbricks.com \
--cc=jthumshirn@suse.de \
--cc=keescook@chromium.org \
--cc=lindar_liu@usish.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=weiyongjun1@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).