From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kees Cook <keescook@chromium.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
John Garry <john.garry@huawei.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Jack Wang <jinpu.wang@profitbricks.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>,
Wei Yongjun <weiyongjun1@huawei.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: sas: Convert timers to use timer_setup()
Date: Tue, 31 Oct 2017 11:56:43 -0400 [thread overview]
Message-ID: <yq14lqfb9ac.fsf@oracle.com> (raw)
In-Reply-To: <20171025100800.GA145125@beast> (Kees Cook's message of "Wed, 25 Oct 2017 03:08:00 -0700")
Kees,
> 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.
Would be good to get John and Jack to take a closer look...
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-10-31 15:57 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 [this message]
2017-10-31 18:13 ` John Garry
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=yq14lqfb9ac.fsf@oracle.com \
--to=martin.petersen@oracle.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=john.garry@huawei.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=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).