From: Richard Cochran <richardcochran@gmail.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3) posix-timers: make it configurable
Date: Sun, 18 Sep 2016 23:11:02 +0200 [thread overview]
Message-ID: <20160918211102.GA14430@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1609181627240.9311@knanqh.ubzr>
On Sun, Sep 18, 2016 at 04:30:21PM -0400, Nicolas Pitre wrote:
> I don't think the driver changes are significant enough to warrant a ACK
> from individual driver maintainers.
>
> Yours would be welcome though. ;-)
Acked-by: Richard Cochran <richardcochran@gmail.com>
> Then I'll resend the whole thing to John as a series and CC netdev.
>
> What do you think?
Sounds ok to me.
Thanks,
Richard
next prev parent reply other threads:[~2016-09-18 21:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 3:47 [PATCH v3) posix-timers: make it configurable Nicolas Pitre
2016-09-15 17:48 ` John Stultz
2016-09-15 17:56 ` Nicolas Pitre
2016-09-15 18:13 ` John Stultz
2016-09-15 18:28 ` Nicolas Pitre
2016-09-15 18:35 ` John Stultz
2016-09-15 18:37 ` Nicolas Pitre
2016-09-15 18:46 ` John Stultz
2016-09-15 19:31 ` Nicolas Pitre
2016-09-15 19:58 ` John Stultz
2016-09-15 21:07 ` Richard Cochran
2016-09-15 21:15 ` Josh Triplett
2016-09-15 21:35 ` Nicolas Pitre
2016-09-15 21:56 ` Josh Triplett
2016-09-16 7:24 ` Richard Cochran
2016-09-17 2:57 ` Nicolas Pitre
2016-09-18 14:35 ` Richard Cochran
2016-09-18 16:54 ` Nicolas Pitre
2016-09-18 18:20 ` Richard Cochran
2016-09-18 18:49 ` Nicolas Pitre
2016-09-18 20:22 ` Richard Cochran
2016-09-18 20:30 ` Nicolas Pitre
2016-09-18 21:11 ` Richard Cochran [this message]
2016-09-15 21:23 ` Richard Cochran
2016-09-16 14:31 ` kbuild test robot
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=20160918211102.GA14430@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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 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.