From: Felipe Balbi <balbi@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: isp1301-omap: Convert timers to use timer_setup()
Date: Tue, 17 Oct 2017 12:42:31 +0300 [thread overview]
Message-ID: <87d15mjek8.fsf@linux.intel.com> (raw)
In-Reply-To: <20171017085243.GA9776@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Hi,
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
>> Kees Cook <keescook@chromium.org> writes:
>> > 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: Felipe Balbi <balbi@kernel.org>
>> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> > Cc: linux-usb@vger.kernel.org
>> > Cc: linux-omap@vger.kernel.org
>> > Signed-off-by: Kees Cook <keescook@chromium.org>
>> > Acked-by: Tony Lindgren <tony@atomide.com>
>>
>> do you want me to take this through my tree?
>>
>> If you wanna take through yours, here's my ack:
>>
>> Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>
> I'll just take it through mine, thanks :)
thanks for confirming. Dropped from my queue.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-17 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:29 [PATCH] usb: isp1301-omap: Convert timers to use timer_setup() Kees Cook
2017-10-17 8:09 ` Felipe Balbi
2017-10-17 8:52 ` Greg Kroah-Hartman
2017-10-17 9:42 ` Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-05 0:53 Kees Cook
2017-10-05 19:27 ` Tony Lindgren
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=87d15mjek8.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).