----- Forwarded message from David Miller davem@davemloft.net -----
Date: Sun, 17 Jan 2016 19:27:17 -0500 (EST) From: David Miller davem@davemloft.net To: amsfield22@gmail.com Cc: mac@melware.de, isdn@linux-pingi.de, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, y2038@lists.linaro.org Subject: Re: [PATCH v3] isdn: divamnt: use y2038-safe ktime_get_ts64() for trace data timestamps X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
From: Alison Schofield amsfield22@gmail.com Date: Fri, 15 Jan 2016 08:51:25 -0800
divamnt stores a start_time at module init and uses it to calculate elapsed time. The elapsed time, stored in secs and usecs, is part of
...............snip
Signed-off-by: Alison Schofield amsfield22@gmail.com Reviewed-by: Arnd Bergmann arnd@arndb.de
Please resubmit this when the net-next tree is open again.
Thank you.
----- End forwarded message -----
Arnd,
How do I know when the net-next tree is open? And, I guess I need to rebase this on the net-next tree before I resend - right?
Thanks! Alison
On Wednesday 17 February 2016 10:48:43 Alison Schofield wrote:
----- End forwarded message -----
Arnd,
How do I know when the net-next tree is open?
The net-next tree is open from the day that -rc1 is released until (iirc) the start of the next merge window when the official kernel is release, and it's closed during the merge window.
And, I guess I need to rebase this on the net-next tree before I resend
Correct.
Arnd