From: Jens Axboe <axboe@kernel.dk>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Ed L. Cashin" <ed.cashin@acm.org>,
linux-block@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] block/aoe: Convert timers to use timer_setup()
Date: Tue, 17 Oct 2017 10:09:25 -0600 [thread overview]
Message-ID: <e883e5c0-f3b6-af74-a06b-e6162f93a32d@kernel.dk> (raw)
In-Reply-To: <CAGXu5jK3aGwt1j=A022y2zvKOqjNxzigHuiUqfJTnqMU4-B7dw@mail.gmail.com>
On 10/16/2017 06:03 PM, Kees Cook wrote:
> On Fri, Oct 6, 2017 at 7:19 AM, Jens Axboe <axboe@kernel.dk> wrote:
>> On 10/05/2017 05:13 PM, 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.
>>
>> Applied to for-4.15/timer
>
> Hi,
>
> I just wanted to check what your timer plans were for merging this
> into -next (I'm doing rebasing to find out which maintainers I need to
> resend patches to, and I noticed block hasn't appeared in -next, but I
> know you've pulled patches...)
It should be in for-next, since I wrote that email. It's in my
for-4.15/timer branch, which is also merged into my for-next branch
(which is the one that Stephen pulls).
--
Jens Axboe
next prev parent reply other threads:[~2017-10-17 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 23:13 [PATCH v2] block/aoe: Convert timers to use timer_setup() Kees Cook
2017-10-06 14:19 ` Jens Axboe
2017-10-17 0:03 ` Kees Cook
2017-10-17 16:09 ` Jens Axboe [this message]
2017-10-17 16:21 ` Jens Axboe
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=e883e5c0-f3b6-af74-a06b-e6162f93a32d@kernel.dk \
--to=axboe@kernel.dk \
--cc=ed.cashin@acm.org \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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