From: Ulrich Obergfell <uobergfe@redhat.com>
To: Don Zickus <dzickus@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] watchdog: parameters to control hard and soft lockup detector individually
Date: Fri, 17 Oct 2014 14:06:56 -0400 (EDT) [thread overview]
Message-ID: <670899746.71006536.1413569216696.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20141014145612.GA135937@redhat.com>
> ----- Original Message -----
> From: "Don Zickus" <dzickus@redhat.com>
> To: "Ulrich Obergfell" <uobergfe@redhat.com>
> Cc: linux-kernel@vger.kernel.org
> Sent: Tuesday, October 14, 2014 4:56:12 PM
> Subject: Re: [PATCH 0/1] watchdog: parameters to control hard and soft lockup detector individually
>
> On Mon, Oct 13, 2014 at 04:32:41PM +0200, Ulrich Obergfell wrote:
>> This post follows up to https://lkml.org/lkml/2014/8/11/329.
>> During the discussion of that patch, Ingo Molnar commented in
>> https://lkml.org/lkml/2014/8/18/577.
>>
>> "The softlockup and hardlockup detection control variables
>> should be in separate flags, inside and outside the kernel -
>> they (should) not relate to each other."
>>
>> Please refer to [PATCH 1/1] for a description of the proposed
>> changes of the 'user interface' in /proc/sys/kernel and kernel
>> command line parameters.
>
> Hi Uli,
>
> Andrew just posted some of your other patches upstream for v3.18-rc1.
> Let's try to rebase these changes on top of those and see what it looks
> like.
>
> Cheers,
> Don
Don,
I rebased the changes and posted a 'version 2' series in
https://lkml.org/lkml/2014/10/17/340
Regards,
Uli
prev parent reply other threads:[~2014-10-17 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 14:32 [PATCH 0/1] watchdog: parameters to control hard and soft lockup detector individually Ulrich Obergfell
2014-10-13 14:32 ` [PATCH 1/1] " Ulrich Obergfell
2014-10-14 14:56 ` [PATCH 0/1] " Don Zickus
2014-10-17 18:06 ` Ulrich Obergfell [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=670899746.71006536.1413569216696.JavaMail.zimbra@redhat.com \
--to=uobergfe@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@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 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).