LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kukjin Kim <kgene@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Anand Moon <moon.linux@yahoo.com>,
Russell King <linux@arm.linux.org.uk>,
Kukjin Kim <kgene@kernel.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Doug Anderson <dianders@chromium.org>,
Sachin Kamat <sachin.kamat@samsung.com>,
Vivek Gautam <gautam.vivek@samsung.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Tushar Behera <tushar.behera@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ARM: exynos_defconfig Enable CONFIG_LOCKUP_DETECTOR.
Date: Sat, 24 Jan 2015 13:55:23 +0900 [thread overview]
Message-ID: <54C325BB.1010904@kernel.org> (raw)
In-Reply-To: <1421137088.8355.1.camel@AMDC1943>
On 01/13/15 17:18, Krzysztof Kozlowski wrote:
> On wto, 2015-01-13 at 00:20 +0530, Anand Moon wrote:
>> On enabling CONFIG_LOCKUP_DETECTOR the kernel to act as a watchdog
>> to detect hard and soft lockups. Enabling CONFIG_LOCKUP_DETECTOR
>> don't introduce much overhead on exyons SOC.
>>
>> CONFIG_LOCKUP_DETECTOR is enabled on multi_v7_defconfig.
>>
>> Changes since v3:
>> * Made commit message more clear
>> * Corrected difference between CONFIG_LOCKUP_DETECTOR and CONFIG_LOCKDEP.
>>
>> Tested on Exynos5422 ODROID XU3 board.
>>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> Signed-off-by: Anand Moon <moon.linux@yahoo.com>
>
> Now it looks okay. My reviewed-by may stay on.
>
Thanks, applied
- Kukjin
prev parent reply other threads:[~2015-01-24 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1421088614-4662-1-git-send-email-moon.linux@yahoo.com>
2015-01-13 8:18 ` Krzysztof Kozlowski
2015-01-24 4:55 ` Kukjin Kim [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=54C325BB.1010904@kernel.org \
--to=kgene@kernel.org \
--cc=dianders@chromium.org \
--cc=gautam.vivek@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moon.linux@yahoo.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sachin.kamat@samsung.com \
--cc=tushar.behera@linaro.org \
--subject='Re: [PATCH v3] ARM: exynos_defconfig Enable CONFIG_LOCKUP_DETECTOR.' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).