All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [v1 0/2] Early boot timestamp fixes
Date: Thu, 15 Jun 2017 15:34:01 +0000	[thread overview]
Message-ID: <3adcc5fa-6e64-13b1-8ad1-e4a43dcf716d@oracle.com> (raw)
In-Reply-To: <1497537659-419752-1-git-send-email-pasha.tatashin@oracle.com>



On 06/15/2017 11:23 AM, David Miller wrote:
> From: Guenter Roeck <linux@roeck-us.net>
> Date: Thu, 15 Jun 2017 08:20:01 -0700
> 
>> On Thu, Jun 15, 2017 at 10:40:57AM -0400, Pavel Tatashin wrote:
>>> Guenter Roeck reported a problem that was introduced by early boot
>>> timestamp changes. Where: tick_get_frequency() returns 0.
>>>
>>> Guenter Roeck: could you please test if these patches fix the issue?
>>>
>> My tests pass with those patches applied, so
>>
>> Tested-by: Guenter Roeck <linux@roeck-us.net>
> 
> Pushed to sparc-next, thanks for testing!
> 
> Pavel, maybe you can add qemu-sparc64 to your test matrix?

Guenter thank you very much for testing it so promptly.

I will setup qemu for sparc64 to test my future changes. This should be 
extremely useful.



  parent reply	other threads:[~2017-06-15 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 14:40 [v1 0/2] Early boot timestamp fixes Pavel Tatashin
2017-06-15 15:20 ` Guenter Roeck
2017-06-15 15:21 ` David Miller
2017-06-15 15:23 ` David Miller
2017-06-15 15:34 ` Pasha Tatashin [this message]
2017-06-15 15:43 ` Pasha Tatashin
2017-06-15 17:57 ` Mark Cave-Ayland
2017-06-15 18:06 ` David Miller
2017-06-15 19:36 ` Guenter Roeck
2017-06-15 20:01 ` Pasha Tatashin
2017-06-15 20:33 ` Guenter Roeck
2017-06-15 21:36 ` Guenter Roeck
2017-06-16 12:17 ` Mark Cave-Ayland
2017-06-16 12:23 ` Mark Cave-Ayland
2017-06-16 16:40 ` David Miller

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=3adcc5fa-6e64-13b1-8ad1-e4a43dcf716d@oracle.com \
    --to=pasha.tatashin@oracle.com \
    --cc=sparclinux@vger.kernel.org \
    /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.