From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753958AbdJaSMe (ORCPT <rfc822;w@1wt.eu>);
        Tue, 31 Oct 2017 14:12:34 -0400
Received: from mail-io0-f178.google.com ([209.85.223.178]:47893 "EHLO
        mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932723AbdJaSMb (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 31 Oct 2017 14:12:31 -0400
X-Google-Smtp-Source: ABhQp+RTboO8ub1tnye/qGXsubcFFXBf7g8McBZNgvrIDsxqLLdnqiPjbfw3vm3DOFWn084HOzeFt7HSoVWkvsYs7tc=
MIME-Version: 1.0
In-Reply-To: <yq1k1zb8b9n.fsf@oracle.com>
References: <20171027091930.GA14728@beast> <1509109031.3135.1.camel@wdc.com>
 <CAGXu5j+z9t28n33e6r9hxRNX1hpkzF4Z5sy308sWYh84whkRfQ@mail.gmail.com>
 <1509470185.12927.1.camel@wdc.com> <yq11slj9qtq.fsf@oracle.com>
 <1509471239.12927.3.camel@wdc.com> <yq1k1zb8b9n.fsf@oracle.com>
From: Kees Cook <keescook@chromium.org>
Date: Tue, 31 Oct 2017 11:12:29 -0700
X-Google-Sender-Auth: KWRzxSZBSqKzmwSGXkEisnbA7pA
Message-ID: <CAGXu5jJNabMzjCSwFjaaF6VcBBD57gG9FgXTBgAHCmbKcb_AHw@mail.gmail.com>
Subject: Re: [PATCH v2] target/iscsi: Convert timers to use timer_setup()
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
        "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>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Oct 31, 2017 at 10:42 AM, Martin K. Petersen
<martin.petersen@oracle.com> wrote:
>
> Bart,
>
>> The tree I tested indeed includes that rebased patch. BTW, since the code
>> touched by that patch has not been modified in the past months, the rebased
>> patch is identical to the patch I posted in May 2017.
>
> OK. Just checking.
>
> So what's the plan here? Should both patches be routed through the timer
> tree?

That was my plan. Does that sound okay?

-Kees

-- 
Kees Cook
Pixel Security