Received: by 10.223.185.116 with SMTP id b49csp3205137wrg; Sun, 25 Feb 2018 16:51:49 -0800 (PST) X-Google-Smtp-Source: AH8x224vgDr1Tza3N3ys6rihwVob6zmp/SwtKfjKwRQmeQIBYh86uVgGSa6LszfcDExNUcgvrxHc X-Received: by 10.101.92.6 with SMTP id u6mr7015105pgr.440.1519606309182; Sun, 25 Feb 2018 16:51:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519606309; cv=none; d=google.com; s=arc-20160816; b=tDLhUv6BCdlro4o8aPWGRcJUuZ8sp+DOxkWMsBPz9gYZAbijqYC/JzJ6ef7e69Db+t iYxNRcHNRcmtAZ/KWL3lkWRNIaSlo72kHLYy9jsJWU/ge0t9J/N6rJ9Jgr41sLE7fLoL Kmk7Cz0Iqy+8M9yzyZF9StMlDbzv+vcYkcQGHUmdjkGwWYTCYh3LBAxSUR+tVKTbsblp VT4f7PRCtDZz9Vl87AxnzctjavfVK9FU4CuX+OlTU6eqkrGJxKAiV5EVPM8HwJNIFhln R46CAQzbYUBoczLCMvVjW41tZ7fM5T9dP3y6Jq6OgMv1NOC6Gd7Ucw5zkAXmuAoJNZVr CPCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=CPmFeIFhbY55BvNmq9hxyeypHuCCD4tHGI0lkSa9L4E=; b=TAKEcA/CmibDFZiN4J/z4kwhLNxx6omp7dNfMX0OktIP+vjBRwrp23ovI7vkfjk6m3 gebMMD35Qa+WSo/ekxVqxbnFWNSJtghySNgjlEO+PUlsAlDzlSTbH/lGTwnLgLy7y5Ko TcfZEsS8qNq1a9tWPtok7mrbUsGKfcAjztOGhD6LKqC8gkx/zBweIldumckuQM67tpBo YFN7Ku6bKOlN+uubZyIiWWlGtVtfKQSTz5EHR0rQLBiHM3iHRxhiGvyqmi8zycf4Z4D7 7EPnWpzZfzZkYSM+M559483DKT63ejdstIn7bUnJN3QOc0V384gGf1XEDt2NH7ldROPG 1mIQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=DmuHUlzV; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z2si5818758pfe.350.2018.02.25.16.51.34; Sun, 25 Feb 2018 16:51:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=DmuHUlzV; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751997AbeBZAuW (ORCPT + 99 others); Sun, 25 Feb 2018 19:50:22 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:35983 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751904AbeBZAuU (ORCPT ); Sun, 25 Feb 2018 19:50:20 -0500 Received: by mail-pf0-f195.google.com with SMTP id 68so5843903pfx.3; Sun, 25 Feb 2018 16:50:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CPmFeIFhbY55BvNmq9hxyeypHuCCD4tHGI0lkSa9L4E=; b=DmuHUlzVlaRHF8O586cJMCcIlsUesdQk3l7gRQdUM3Dx4e0ghuf+pKvO9P5lZIV8EZ aQ6OngRdPRTtSR6UsFERdoYV7xKYHLYEdXxxOQhnDeBNE7vx37cxhXc1ABTWx9Tr+2qO LWWmQ2XCias9wMJBbjCWEPHOncm6BBDasj1K26XjJpu9rXXyLT9x29Wuht1ebMIdW5Ce qnftMSunm4LJqueKIIasTpLhTKZWqGBRDRGhTyjQY7FpMm2D6Or+6kV9LgDjlinoGdZm +QP463FeE5U6uUx37VKjDzuMsSkQLxFKhu0WxveQ4AYARB9Uc/Nh9mvGmRzVl/3qkr5u L1hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CPmFeIFhbY55BvNmq9hxyeypHuCCD4tHGI0lkSa9L4E=; b=NymRL/BMe0s1Oy3XYQTDnD/1mB1ylG7EUhM3tvy9VGmqgbM416x0lrjTUsNnpXzRBB vP/HJqWNRooIWJUrSnoAS9V+Z9N8+T7YJ5rI18P1bKsnrFGOwGCGULOmIeHtQx8r4XNn yhc4WtPu6Wu0fYzhkO8huph9DANAg4bYfn8C2bxrd3lcVfJqzQPaKxJC0djzWCKIT0O7 g+DmUQ0H9yeYsp3Tgp7St6xnEhCZA/F+owVWUttgBMgprQPZCj0kM6ngGyIWGp0ltivM 64vLH7qGWw8nGFH6fW7esfGNScPgCI9T4youz2AwZS5cjUJfKGaGdZGfzeIRfSVi8LC4 i2+w== X-Gm-Message-State: APf1xPA3+yQXkKq7/V4pRpPacqY1DxOXwGiAoV3mMLYAU2Q79Jh/fejz wO41aXL5V81hFKka822E5Dc= X-Received: by 10.101.93.73 with SMTP id e9mr7136237pgt.264.1519606220216; Sun, 25 Feb 2018 16:50:20 -0800 (PST) Received: from server.roeck-us.net (108-223-40-66.lightspeed.sntcca.sbcglobal.net. [108.223.40.66]) by smtp.gmail.com with ESMTPSA id y27sm15600514pfi.186.2018.02.25.16.50.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Feb 2018 16:50:19 -0800 (PST) Subject: Re: [PATCH v4 00/10] watchdog/hpwdt: Update driver to use watchdog core. To: Jerry Hoemann , wim@linux-watchdog.org Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, rwright@hpe.com, maurice.a.saldivar@hpe.com, mingo@kernel.org, marcus.folkesson@gmail.com References: <20180225213259.2861-1-jerry.hoemann@hpe.com> From: Guenter Roeck Message-ID: <30f31e66-3d32-516f-f0a4-f3fba13b5677@roeck-us.net> Date: Sun, 25 Feb 2018 16:50:18 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180225213259.2861-1-jerry.hoemann@hpe.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/25/2018 01:32 PM, Jerry Hoemann wrote: > == v4 == > > Modifications from prior version: > > Manual merging and patch reordering has caused minor white > space and diff changes. Such change shouldn't have effected > the logic and are omitted below: > For the most part looks good except for the nitpicks, and the change log below no longer matches reality since you added a new patch 1 which is not reflected in the patch numbering (you added the reference to the new patch at the end, so according to the log you now have two patches #1). Thanks, Guenter > Patch 001 Remove legacy NMI sourcing. > 1) Updated patch documentation to reflect Spectre concerns. > 2) Restored comment at #endif > > Patch 002 watchdog/hpwdt: remove include files no longer > 1) Squashed onto Patch001. > > Patch 0003: watchdog/hpwdt: Update nmi_panic message. > 1) Unchanged > > > Patch 0004: watchdog/hpwdt: white space changes > 1) Redacted. > > Patch 0005: watchdog/hpwdt: Update Module info. > 1) Now Patch 0004 > 2) Update only module description to reflect branding changes. > 3) Rest of patch redacted. > > Patch 0006 Select CORE > 1) Merged with 0007 > > Patch 0007 Modify to use watchdog core > 1) squashed on Patch 0006. > 2) Now Patch 0005 > 3) Requested white space changes. > 4) Use "wdd" for watchdog_device like other watchdog drivers do > > Patch 0008 Programable-Pretimeout > 1) hpwdt_settimeout re-worked to take into account timeout <= pretimeout. > Patterned after watchdog_set_timeout. > 2) hpwdt_set_pretimeout re-worked to take into account requested > pretimeout <= timeout. > 3) Clarify patch doc to reflect above. > > Patch 0009 condition-early-return-of-NMI > 1) Requested syntatic surgar. > 2) Now Patch 0006 > > Patch 0010 remove-allow_kdump > 1) Now Patch 0007 > > Patch 0011 Add-dynamic-debug > 1) Now Patch 0009 > 2) Typo fix > 3) New dev_dbg resulting from changes to set timeout and pretimeout. > > Patch 0012 Update driver version. > 1) Now Patch 0010 > > > New Patch > 1) Patch 0001 Update Copyright > > > > == v3 == > > Incorperating code review feedback. > > 1) Patch 0003: Use existing hex_byte_pack instead of creating new function. > 2) Patch 0005: Redacted change in module_param permission. > 3) Patch 0006: switch from pr_debug etc., to dev_dbg where possible. > 4) Patch 0006: No longer updating soft_margin post module load. > 5) Patch 0006: Initialize hpwdt_dev.parent before registering watchdog. > 6) Patch 0006: Redacted change to dev_info message w.r.t. allow_kdump > 7) Patch 0006 & 0007: Reorder patches to maintain bisectability. > 8) Patch 0008: Change pr_debug to dev_dbg > 9) Patch 0010: Change dev_info message w.r.t. allow_kdump where feature > is removed. > > Note, I am explicitly ignoring the checkpatch error on Patch 0008 > for specifying permisson of "0" instead of "0000". > > == v2 == > > 1) Fix compiler error when CONFIG_HPWDT_NMI_DECODING is not defined. > > 2) Break out driver version change to its own patch (0011). > > > == v1 == > > The primary purposes of this patch set are to > > 1) Update the hpwdt driver to use the watchdog core. > 2) Reduce complexity by removing unnecessary features. > 3) Add customer requested features like optional pretimeout. > 4) Enhance readability/maintainability of the driver. > > The size of the resultant driver is reduced from over 900 > lines to 350 lines. > > Patch 1& 2 remove legacy NMI sourcing. > Patch 3 adds useful indication of NMI cause to panic message > Patch 4 & 5 are general cleanup > Patch 6 & 7 updates the driver to user the watchdog core. > Patch 8 makes the pretimeout NMI programmable. > Patch 9 modifies whether the NMI handler claims the NMI. > Patch 10 retracts the allow_kdump module parameter. > > > > Jerry Hoemann (10): > watchdog/hpwdt: Update copyright. > watchdog/hpwdt: Remove legacy NMI sourcing. > watchdog/hpwdt: Update nmi_panic message. > watchdog/hpwdt: Update Module info. > watchdog/hpwdt: Modify to use watchdog core. > watchdog/hpwdt: condition early return of NMI handler on iLO5 > watchdog/hpwdt: remove allow_kdump module parameter. > watchdog/hpwdt: Programable Pretimeout NMI > watchdog/hpwdt: Add dynamic debug > watchdog/hpwdt: Update driver version. > > drivers/watchdog/Kconfig | 1 + > drivers/watchdog/hpwdt.c | 789 +++++++---------------------------------------- > 2 files changed, 121 insertions(+), 669 deletions(-) >