From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"varun@chelsio.com" <varun@chelsio.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"jiangyilism@gmail.com" <jiangyilism@gmail.com>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Subject: Re: [PATCH v2] target/iscsi: Convert timers to use timer_setup()
Date: Tue, 31 Oct 2017 13:20:49 -0400 [thread overview]
Message-ID: <yq11slj9qtq.fsf@oracle.com> (raw)
In-Reply-To: <1509470185.12927.1.camel@wdc.com> (Bart Van Assche's message of "Tue, 31 Oct 2017 17:16:26 +0000")
Bart,
> That tree passed the iSCSI target tests I ran so feel free to add my
> Reviewed-by and Tested-by to [PATCH v2] target/iscsi: Convert timers
> to use timer_setup().
Is that with your rebased patch from a few days ago?
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"varun@chelsio.com" <varun@chelsio.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"jiangyilism@gmail.com" <jiangyilism@gmail.com>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Subject: Re: [PATCH v2] target/iscsi: Convert timers to use timer_setup()
Date: Tue, 31 Oct 2017 17:20:49 +0000 [thread overview]
Message-ID: <yq11slj9qtq.fsf@oracle.com> (raw)
In-Reply-To: <1509470185.12927.1.camel@wdc.com> (Bart Van Assche's message of "Tue, 31 Oct 2017 17:16:26 +0000")
Bart,
> That tree passed the iSCSI target tests I ran so feel free to add my
> Reviewed-by and Tested-by to [PATCH v2] target/iscsi: Convert timers
> to use timer_setup().
Is that with your rebased patch from a few days ago?
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "keescook\@chromium.org" <keescook@chromium.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"varun\@chelsio.com" <varun@chelsio.com>,
"target-devel\@vger.kernel.org" <target-devel@vger.kernel.org>,
"jiangyilism\@gmail.com" <jiangyilism@gmail.com>,
"nab\@linux-iscsi.org" <nab@linux-iscsi.org>
Subject: Re: [PATCH v2] target/iscsi: Convert timers to use timer_setup()
Date: Tue, 31 Oct 2017 13:20:49 -0400 [thread overview]
Message-ID: <yq11slj9qtq.fsf@oracle.com> (raw)
In-Reply-To: <1509470185.12927.1.camel@wdc.com> (Bart Van Assche's message of "Tue, 31 Oct 2017 17:16:26 +0000")
Bart,
> That tree passed the iSCSI target tests I ran so feel free to add my
> Reviewed-by and Tested-by to [PATCH v2] target/iscsi: Convert timers
> to use timer_setup().
Is that with your rebased patch from a few days ago?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-10-31 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 9:19 [PATCH v2] target/iscsi: Convert timers to use timer_setup() Kees Cook
2017-10-27 9:19 ` Kees Cook
2017-10-27 12:57 ` Bart Van Assche
2017-10-27 12:57 ` Bart Van Assche
2017-10-31 0:04 ` Kees Cook
2017-10-31 0:04 ` Kees Cook
2017-10-31 17:16 ` Bart Van Assche
2017-10-31 17:16 ` Bart Van Assche
2017-10-31 17:20 ` Martin K. Petersen [this message]
2017-10-31 17:20 ` Martin K. Petersen
2017-10-31 17:20 ` Martin K. Petersen
2017-10-31 17:34 ` Bart Van Assche
2017-10-31 17:34 ` Bart Van Assche
2017-10-31 17:42 ` Martin K. Petersen
2017-10-31 17:42 ` Martin K. Petersen
2017-10-31 17:42 ` Martin K. Petersen
2017-10-31 18:12 ` Kees Cook
2017-10-31 18:12 ` Kees Cook
2017-10-31 18:13 ` Martin K. Petersen
2017-10-31 18:13 ` Martin K. Petersen
2017-10-31 18:13 ` 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=yq11slj9qtq.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@wdc.com \
--cc=jiangyilism@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
--cc=varun@chelsio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.