From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752402AbbBEXWc (ORCPT ); Thu, 5 Feb 2015 18:22:32 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:37823 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751132AbbBEXWc (ORCPT ); Thu, 5 Feb 2015 18:22:32 -0500 Date: Thu, 5 Feb 2015 15:22:30 -0800 From: Andrew Morton To: Don Zickus Cc: LKML Subject: Re: [PATCH 0/9] watchdog: internally split softlockup and hardlockup Message-Id: <20150205152230.e978767c9c5eeb3b97be99f8@linux-foundation.org> In-Reply-To: <1423168825-156238-1-git-send-email-dzickus@redhat.com> References: <1423168825-156238-1-git-send-email-dzickus@redhat.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Feb 2015 15:40:16 -0500 Don Zickus wrote: > The hardlockup and softockup had always been tied together. Due to the request > of KVM folks, they had a need to have one enabled but not the other. > Internally rework the code to split things apart more cleanly. > > There is a bunch of churn here, but the end result should be code that should > be easier to maintain and fix without knowing the internals of what is going > on. We're late in -rc7, which is not a good time for "a bunch of churn". So I'll park this series for consideration after 3.19 has been released. I'll let you know if it has seriously bitrotted by then.