From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: Re: [clockevents] WARNING: CPU: 0 PID: 0 at kernel/time/tick-oneshot.c:32 tick_stop_event()
Date: Mon, 23 Jun 2014 17:39:25 +0800 [thread overview]
Message-ID: <20140623093925.GA1454@localhost> (raw)
In-Reply-To: <CAKohpomtHuXP0Q9QnWvJj1d2O=AewMR+nVNE3N_KFJkMpcCHYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
Hi Viresh,
On Mon, Jun 23, 2014 at 02:02:25PM +0530, Viresh Kumar wrote:
> On 23 June 2014 13:50, Jet Chen <jet.chen@intel.com> wrote:
> > Hi Viresh,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://git.linaro.org/people/vireshk/linux tick/ONESHOT-STOPPED
>
> Hi Jet/Fengguang,
>
> Why did your scripts Cc'd LKML for this report? It never used to
> happen for my trees Atleast.
Yeah our build error reports are mostly private emails. However we do
CC LKML for runtime regressions - because there is no easy way for us
to tell whether the reported regression has reached more people.
> These patches haven't been posted to LKML yet and sending
> reports there for these wouldn't be good for their fate :)
Sorry if it hurts. :)
> Anyway, will look at what broke. Thanks.
Thank you!
Cheers,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jet Chen <jet.chen@intel.com>, LKP <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [clockevents] WARNING: CPU: 0 PID: 0 at kernel/time/tick-oneshot.c:32 tick_stop_event()
Date: Mon, 23 Jun 2014 17:39:25 +0800 [thread overview]
Message-ID: <20140623093925.GA1454@localhost> (raw)
In-Reply-To: <CAKohpomtHuXP0Q9QnWvJj1d2O=AewMR+nVNE3N_KFJkMpcCHYA@mail.gmail.com>
Hi Viresh,
On Mon, Jun 23, 2014 at 02:02:25PM +0530, Viresh Kumar wrote:
> On 23 June 2014 13:50, Jet Chen <jet.chen@intel.com> wrote:
> > Hi Viresh,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://git.linaro.org/people/vireshk/linux tick/ONESHOT-STOPPED
>
> Hi Jet/Fengguang,
>
> Why did your scripts Cc'd LKML for this report? It never used to
> happen for my trees Atleast.
Yeah our build error reports are mostly private emails. However we do
CC LKML for runtime regressions - because there is no easy way for us
to tell whether the reported regression has reached more people.
> These patches haven't been posted to LKML yet and sending
> reports there for these wouldn't be good for their fate :)
Sorry if it hurts. :)
> Anyway, will look at what broke. Thanks.
Thank you!
Cheers,
Fengguang
next prev parent reply other threads:[~2014-06-23 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 8:20 [clockevents] WARNING: CPU: 0 PID: 0 at kernel/time/tick-oneshot.c:32 tick_stop_event() Jet Chen
2014-06-23 8:20 ` Jet Chen
2014-06-23 8:32 ` Viresh Kumar
2014-06-23 8:32 ` Viresh Kumar
2014-06-23 9:39 ` Fengguang Wu [this message]
2014-06-23 9:39 ` Fengguang Wu
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=20140623093925.GA1454@localhost \
--to=fengguang.wu@intel.com \
--cc=lkp@lists.01.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.