mbox series

[GIT,PULL,0/2] Few timekeeping items for 4.19

Message ID 1531426641-20076-1-git-send-email-john.stultz@linaro.org
Headers show
Series Few timekeeping items for 4.19 | expand

Message

John Stultz July 12, 2018, 8:17 p.m. UTC
Hey Thomas,
  I had a few other items in my stack here, but you've already
queued them in -tip, so here's what I have left.

Let me know if you have any objections or feedback for change.

thanks
-john

Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Miroslav Lichvar <mlichvar@redhat.com>
Cc: Richard Cochran <richardcochran@gmail.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Stephen Boyd <sboyd@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org

The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:

  Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)

are available in the git repository at:

  https://git.linaro.org/people/john.stultz/linux.git fortglx/4.19/time

for you to fetch changes up to b061c7a513afe14a68af41cec7c3476befc40e95:

  timekeeping: Update multiplier when NTP frequency is set directly (2018-07-10 12:44:25 -0700)

----------------------------------------------------------------
John Stultz (1):
      selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock adjustments are in progress

Miroslav Lichvar (1):
      timekeeping: Update multiplier when NTP frequency is set directly

 kernel/time/timekeeping.c                 | 36 ++++++++++++++++++++++++++++++------
 tools/testing/selftests/timers/raw_skew.c |  5 +++++
 2 files changed, 35 insertions(+), 6 deletions(-)

-- 
2.7.4

Comments

Thomas Gleixner July 12, 2018, 8:26 p.m. UTC | #1
John,

On Thu, 12 Jul 2018, John Stultz wrote:

>   I had a few other items in my stack here, but you've already

> queued them in -tip, so here's what I have left.


Did I miss you replying on them that you picked them up? Normally when I
see that you or Daniel picked something up I happily move the mails to the
done folder unless I see something horrible.

> Let me know if you have any objections or feedback for change.


One small request for the next pull request. Please write a short summary,
optionally in a tag, then pulling the tag adds it to the merge commit message.
But plain in the pull request mail is fine as well.

Thanks,

	tglx
John Stultz July 12, 2018, 8:34 p.m. UTC | #2
On Thu, Jul 12, 2018 at 1:26 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Thu, 12 Jul 2018, John Stultz wrote:

>

>>   I had a few other items in my stack here, but you've already

>> queued them in -tip, so here's what I have left.

>

> Did I miss you replying on them that you picked them up? Normally when I

> see that you or Daniel picked something up I happily move the mails to the

> done folder unless I see something horrible.


No, that's my fault. I'll try to be better about making that clear so
you don't duplicate work. You're just much faster then I am :)

>> Let me know if you have any objections or feedback for change.

>

> One small request for the next pull request. Please write a short summary,

> optionally in a tag, then pulling the tag adds it to the merge commit message.

> But plain in the pull request mail is fine as well.


Sure, I'll try to take a swing at this next time, I've not done much
with git tags (other then trying to do a signature tag long ago when I
still had a valid gpg key :)

thanks
-john