[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokYfdY+40kmhgrC6Yr9vfv4GtAW2Ph3+=57YbfmJsnU9w@mail.gmail.com>
Date: Tue, 1 Apr 2014 10:02:43 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Kevin Hilman <khilman@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Frédéric Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, Tejun Heo <tj@...nel.org>,
Li Zefan <lizefan@...wei.com>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Cgroups <cgroups@...r.kernel.org>
Subject: Re: [RFC 2/4] timer: don't migrate pinned timers
On 31 March 2014 21:26, Kevin Hilman <khilman@...aro.org> wrote:
> Viresh Kumar <viresh.kumar@...aro.org> writes:
>> + if (is_pinned) {
>> + pr_warn("%s: can't migrate pinned timer: %p, removing it\n",
>> + __func__, timer);
>
> printk message will be confusing: removing it from what?
Hmm.. So, I am looking to do two modifications here. Just need inputs
if that would be the right thing to do:
- do a WARN() here as these timers should have been already removed
- change print to: "can't migrate pinned timer %p, deactivating timer"
Looks fine?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists