From: Ingo Molnar <mingo@kernel.org>
To: anish singh <anish198519851985@gmail.com>
Cc: akpm@linux-foundation.org, dzickus@redhat.com,
tglx@linutronix.de, chuansheng.liu@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [Watchdog][Trivial] Added comments to explain watchdog_disabled variable
Date: Wed, 13 Feb 2013 10:21:01 +0100 [thread overview]
Message-ID: <20130213092101.GD7630@gmail.com> (raw)
In-Reply-To: <CAK7N6vpT_X7s7Vid0-EYenb0w7k=nL8d-ov=fExFMuSYcV47Wg@mail.gmail.com>
* anish singh <anish198519851985@gmail.com> wrote:
> Is the below patch picked up?
>
> On Sun, Feb 3, 2013 at 9:31 PM, anish kumar <anish198519851985@gmail.com> wrote:
> > From: anish kumar <anish198519851985@gmail.com>
> >
> > This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is multifold.
> > Uses are:
> > 1. Check if smpboot_register_percpu_thread function passed.
> > 2. Makes sure that user enables and disables the watchdog in sequence
> > i.e. enable watchdog->disable watchdog->enable watchdog
> > Unlike enable watchdog->enable watchdog which is wrong.
> >
> > Signed-off-by: anish kumar <anish198519851985@gmail.com>
> > ---
> > kernel/watchdog.c | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> > index 75a2ab3..87a19aa 100644
> > --- a/kernel/watchdog.c
> > +++ b/kernel/watchdog.c
> > @@ -518,6 +518,11 @@ int proc_dowatchdog(struct ctl_table *table, int write,
> > return ret;
> >
> > set_sample_period();
> > + /*
> > + * We shouldn't enable watchdog threads if it is
> > + * disabled.This is done by watchdog_disabled
> > + * variable check in watchdog_*_all_cpus function.
It has two grammatic and a stylistic error in it, plus misses
the convention that function names are mentioned with a '()'.
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-13 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 16:01 [PATCH] [Watchdog][Trivial] Added comments to explain watchdog_disabled variable anish kumar
2013-02-13 7:17 ` anish singh
2013-02-13 9:21 ` Ingo Molnar [this message]
2013-02-13 9:58 ` anish singh
2013-02-15 16:29 ` Don Zickus
2013-02-16 8:42 ` Ingo Molnar
2013-02-16 11:38 ` anish kumar
-- strict thread matches above, loose matches on Subject: below --
2013-02-16 12:14 anish kumar
2013-02-18 20:48 ` Don Zickus
2013-03-06 11:47 ` anish singh
2013-03-07 15:40 ` Don Zickus
2013-02-01 13:49 anish kumar
2013-02-01 14:59 ` Don Zickus
2013-02-02 3:16 ` anish kumar
2013-02-01 13:33 anish kumar
2013-02-01 13:50 ` anish kumar
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=20130213092101.GD7630@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anish198519851985@gmail.com \
--cc=chuansheng.liu@intel.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.