Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp120194imj; Wed, 13 Feb 2019 05:44:21 -0800 (PST) X-Google-Smtp-Source: AHgI3Iaoe7qY4RddXUtHmsBcQV2Ckh18Fn8PhTHbm9ZkeEqQ69U4qafaK+KDS8tC7VGsmjoQf6iJ X-Received: by 2002:a17:902:9884:: with SMTP id s4mr584725plp.1.1550065461070; Wed, 13 Feb 2019 05:44:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550065461; cv=none; d=google.com; s=arc-20160816; b=pnMuqj216imQiboe617hVUOdYDHSRpVBR3Vjwogx6kbvo51CwloNntYM8rIE6HmXbv VI9LxHT/Dd6XiV5vPj4qrCmED9peJAO8pkTsAvKteu67K/aq0erCQsQR4Hm15Es+oxAV hwGvPG8r18QrEeywEayYCPnmhp3qYOf7xKRLjdHYMsi1wK7eUPv6kPQpQ+UNRzLvRbBc zdrhNUt0gzffxiQJmBgOeumIuzw5Ho3dUHRNZT6clHnYSkOFUSr1gQ7myebihETc21KT GV1rumZvsE/B/LsVprQedA5a5gHa7e5LUsj6djBXptiJa+5v1WLdR8tamt9Y97dW1iH4 4P0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=7igWnWLapM2l5Cf86KYgVsFxpPX+kzXbJCO1ysZUG8U=; b=fWG07QzDrOjK8atYMa5UuN6RnDlJ58dpslPWKl88KnVj/MVWqDjCebcINi4t47+cCY YG+WetAwk7w5RpViPWz/AXC9gZJRV+DmxeUouXwBCqdl2YB9/e0HWjz7IBPxT0gH2OZN noAfWtD8n0ArnqctGEKEsIXCoyNKNuhxu03+Wgt/PJF2gsLAvQC/i0MrJFhuEBL7LW3m hMgAqVAh/aYMfGkfb1gRi70BahW3QkocMqMj+qAOLA0WMsIofY8ofzzOmjoqo41kIQcS a00YKFZhGVNY5Ddpx3Wy7liNiH0UcQUTginayodBZaK5lIy/e7OC5oG/452dLI4P+xsA di1w== ARC-Authentication-Results: i=1; mx.google.com; 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 n3si16916550pfn.285.2019.02.13.05.44.04; Wed, 13 Feb 2019 05:44:21 -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; 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 S2388241AbfBMKJ1 (ORCPT + 99 others); Wed, 13 Feb 2019 05:09:27 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:50732 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727580AbfBMKJ0 (ORCPT ); Wed, 13 Feb 2019 05:09:26 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D2193A78; Wed, 13 Feb 2019 02:09:25 -0800 (PST) Received: from e112298-lin.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 7205A3F575; Wed, 13 Feb 2019 02:09:24 -0800 (PST) From: Julien Thierry To: linux-kernel@vger.kernel.org Cc: liwei391@huawei.com, Julien Thierry , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Marc Zyngier Subject: [PATCH] genirq: Fix wrong name in request_percpu_nmi() description Date: Wed, 13 Feb 2019 10:09:19 +0000 Message-Id: <1550052559-41250-1-git-send-email-julien.thierry@arm.com> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ready_percpu_nmi() was the previous name of prepare_percpu_nmi(). Update request_percpu_nmi() comment with the correct function name. Signed-off-by: Julien Thierry Reported-by: Li Wei Cc: Thomas Gleixner Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Marc Zyngier --- kernel/irq/manage.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Note: This issue is in next, not yet in mainline. Should apply cleanly on top of next. diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c index aea87ec..9ec34a2 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -2431,8 +2431,8 @@ int __request_percpu_irq(unsigned int irq, irq_handler_t handler, * @dev_id: A percpu cookie passed back to the handler function * * This call allocates interrupt resources for a per CPU NMI. Per CPU NMIs - * have to be setup on each CPU by calling ready_percpu_nmi() before being - * enabled on the same CPU by using enable_percpu_nmi(). + * have to be setup on each CPU by calling prepare_percpu_nmi() before + * being enabled on the same CPU by using enable_percpu_nmi(). * * Dev_id must be globally unique. It is a per-cpu variable, and * the handler gets called with the interrupted CPU's instance of -- 1.9.1