From: Mike Snitzer <snitzer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Michael Lyle <mlyle@lyle.org>, Kees Cook <keescook@chromium.org>,
dm-devel@redhat.com, LKML <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org, linux-bcache@vger.kernel.org,
Shaohua Li <shli@fb.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: md: Convert timers to use timer_setup()
Date: Tue, 24 Oct 2017 14:15:55 -0400 [thread overview]
Message-ID: <20171024181555.GA22647@redhat.com> (raw)
In-Reply-To: <D294B3CB-45BC-49B2-A9DD-AB0A01CCB444@kernel.dk>
On Wed, Oct 18 2017 at 11:12pm -0400,
Jens Axboe <axboe@kernel.dk> wrote:
>
> > On Oct 18, 2017, at 9:06 PM, Kees Cook <keescook@chromium.org> wrote:
> >
> >> On Mon, Oct 16, 2017 at 8:06 PM, Michael Lyle <mlyle@lyle.org> wrote:
> >>> On 10/16/2017 05:01 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.
> >>>
> >>> Cc: Kent Overstreet <kent.overstreet@gmail.com>
> >>> Cc: Shaohua Li <shli@kernel.org>
> >>> Cc: Alasdair Kergon <agk@redhat.com>
> >>> Cc: Mike Snitzer <snitzer@redhat.com>
> >>> Cc: dm-devel@redhat.com
> >>> Cc: linux-bcache@vger.kernel.org
> >>> Cc: linux-raid@vger.kernel.org
> >>> Signed-off-by: Kees Cook <keescook@chromium.org>
> >>
> >> This looks good to me-- I'm fine with Jens or someone else picking this
> >> up directly, or would take a bcache-specific one to apply to my tree.
> >>
> >> Reviewed-by: Michael Lyle <mlyle@lyle.org>
> >
> > Jens, can you pick this up, or would you prefer I split it up?
Jens, would you be OK picking it up from patchwork? If so, see:
https://patchwork.kernel.org/patch/10010303/
You can add mine too:
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
next prev parent reply other threads:[~2017-10-24 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 0:01 [PATCH] md: Convert timers to use timer_setup() Kees Cook
2017-10-17 2:12 ` Shaohua Li
2017-10-17 2:23 ` Kees Cook
2017-10-17 3:06 ` Michael Lyle
2017-10-19 3:06 ` Kees Cook
2017-10-19 3:12 ` Jens Axboe
2017-10-24 18:15 ` Mike Snitzer [this message]
2017-10-24 18:18 ` 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=20171024181555.GA22647@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=shli@fb.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).