All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
To: Kees Cook <keescook@chromium.org>,
	"Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alex Elder <elder@kernel.org>,
	greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH v2] staging: greybus: Convert timers to use timer_setup()
Date: Fri, 3 Nov 2017 21:49:11 +0000	[thread overview]
Message-ID: <4d572362-5fe3-8a14-3a05-cadc73914e0b@linaro.org> (raw)
In-Reply-To: <CAGXu5jKrhWvLo+TEGO_+nXzDnb-RVJWQz34idm0t78cgQGPidA@mail.gmail.com>



On 03/11/17 20:21, Kees Cook wrote:
> On Mon, Oct 30, 2017 at 5:05 PM, Kees Cook <keescook@chromium.org> wrote:
>> On Mon, Oct 30, 2017 at 5:01 PM,  <pure.logic@nexus-software.ie> wrote:
>>> There's a separate change to loopback.c an old patch ARAIR that will subtract use of the timer from loopback.c so you can skip that bit.
>>
>> Okay, cool. Since the operation.c change is trivial, I'll include it
>> in the giant tree-wide patch that will (hopefully) land in -rc1.
> 
> I forgot to ask: will the patch for loopback.c that removes the timers
> get posted in the next couple days? I just want to make sure the timer
> conversions don't get blocked behind this.

Yep.

I should get that out tomorrow at some stage.

  reply	other threads:[~2017-11-03 21:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 14:49 [PATCH v2] staging: greybus: Convert timers to use timer_setup() Kees Cook
2017-10-24 15:54 ` Bryan O'Donoghue
2017-10-30 11:32   ` Johan Hovold
2017-10-30 11:35     ` Bryan O'Donoghue
2017-10-30 11:38       ` Johan Hovold
2017-10-30 11:44         ` Bryan O'Donoghue
2017-10-30 11:48           ` Johan Hovold
2017-10-30 21:37             ` Kees Cook
2017-10-31  0:01               ` pure.logic
2017-10-31  0:05                 ` Kees Cook
2017-11-03 20:21                   ` Kees Cook
2017-11-03 21:49                     ` Bryan O'Donoghue [this message]
2017-11-03 21:49                       ` Kees Cook
2017-10-30 11:35   ` Johan Hovold

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=4d572362-5fe3-8a14-3a05-cadc73914e0b@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pure.logic@nexus-software.ie \
    /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.