From: Ingo Molnar <mingo@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [GIT PULL] A few timekeeping items for 4.4
Date: Tue, 20 Oct 2015 09:59:14 +0200 [thread overview]
Message-ID: <20151020075914.GA4127@gmail.com> (raw)
In-Reply-To: <CALAqxLVYGG7_r4BMx6AWsWpGXjibKOcRpWwBZPSWBCJAYPtJ=A@mail.gmail.com>
* John Stultz <john.stultz@linaro.org> wrote:
> Hey Thomas,
>
> I've been bad this cycle with picking up changes, so apologies if I
> missed anything.
>
> thanks
> -john
>
> The following changes since commit 9ffecb10283508260936b96022d4ee43a7798b4c:
>
> Linux 4.3-rc3 (2015-09-27 07:50:08 -0400)
>
> are available in the git repository at:
>
> https://git.linaro.org/people/john.stultz/linux.git fortglx/4.4/time
>
> for you to fetch changes up to 090e2edb4171dae4872c4eaae972dd3ccf96d4a8:
>
> net: sfc: avoid using timespec (2015-10-01 09:59:24 -0700)
>
> ----------------------------------------------------------------
> Arnd Bergmann (5):
> ntp/pps: use timespec64 for hardpps()
> ntp/pps: replace getnstime_raw_and_real with 64-bit version
> ntp: use timespec64 in sync_cmos_clock
> ntp/pps: use y2038 safe types in pps_event_time
> net: sfc: avoid using timespec
>
> drivers/net/ethernet/sfc/ptp.c | 30 +++++++++++++++---------------
> drivers/pps/kapi.c | 4 ++--
> include/linux/pps_kernel.h | 16 ++++++++--------
> include/linux/timekeeping.h | 4 ++--
> include/linux/timex.h | 2 +-
> kernel/time/ntp.c | 16 ++++++++--------
> kernel/time/ntp_internal.h | 2 +-
> kernel/time/timekeeping.c | 14 +++++++-------
> 8 files changed, 44 insertions(+), 44 deletions(-)
Could you please also post these as patches?
Thanks,
Ingo
prev parent reply other threads:[~2015-10-20 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:23 John Stultz
2015-10-20 7:59 ` Ingo Molnar [this message]
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=20151020075914.GA4127@gmail.com \
--to=mingo@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome