From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 366A9C10DCE for ; Wed, 18 Mar 2020 05:44:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0E82E20724 for ; Wed, 18 Mar 2020 05:44:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="auMuif27" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726954AbgCRFo2 (ORCPT ); Wed, 18 Mar 2020 01:44:28 -0400 Received: from mail-pg1-f196.google.com ([209.85.215.196]:47074 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726478AbgCRFo2 (ORCPT ); Wed, 18 Mar 2020 01:44:28 -0400 Received: by mail-pg1-f196.google.com with SMTP id y30so13027690pga.13 for ; Tue, 17 Mar 2020 22:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=qXY2yMRGwktYokk3pPFwmmTxw2SIkRhzk6Ye/AepEnM=; b=auMuif27BF2tfyRqSNTt4zSVURfB7x5ZyhtvFy0jfEjowqXES6bMXaYbo9Rcjq9sOO NkXoBSCwuP0ZDQF4xMbnZXE2eiWzYeLKBPHB0T+1ep2X1MfnosDT4wsHaJ9PVplBUgph 5joOAvaRgGFjqKtAtGLxOd6crzo+aegDG7PVY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=qXY2yMRGwktYokk3pPFwmmTxw2SIkRhzk6Ye/AepEnM=; b=aPaPvrdG0wC7nbkR0hMfwZFY4918POwsZx0wMQ68p7e10sAnAtjPf7eb/BcfABd7yp /P6oKlkP9i5NYyvTNir7HAGjJ9RK6529GrrnqeG4vwGgVWaVal5Ci+XcHT10y0odauTz yGyqpmUzX32cEpldl9n0EhMavjpXRBpYMtVQ0nnIEZnfcDE1YR4sIGNbk4UbWI6Nz9hF ceTysdynu6ggiGs2jM8BDBwt+j7RJrgak7LQ897XT23GFjC+gxfByliYX0/sorxeuTe5 +G6pjLLYMurddL4r0LOgI8ZoGscDBw5Hq7YziE0rommp+T6CT74lIeTbOw+2qqKEw21Q 7Lxg== X-Gm-Message-State: ANhLgQ0m1Lqn3z7IzjcOWcwTq4wz794exPnjwfvoXNtVV3azhtyW07RY d91IRM7sCKBMTAs2DTrCFxpD7r882IE= X-Google-Smtp-Source: ADFU+vsYBFmDXYadiM2XWYH/z8MFjrQ3chr28RyzZ4TN+iHPIz4KZzaFkI1eus8KAFNzwyVqrvROsA== X-Received: by 2002:a65:458e:: with SMTP id o14mr2875894pgq.323.1584510266817; Tue, 17 Mar 2020 22:44:26 -0700 (PDT) Received: from smtp.gmail.com ([2620:15c:202:1:fa53:7765:582b:82b9]) by smtp.gmail.com with ESMTPSA id e11sm5005003pfj.95.2020.03.17.22.44.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Mar 2020 22:44:26 -0700 (PDT) From: Stephen Boyd To: Jonathan Corbet Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: [PATCH] docs: locking: Add 'need' to hardirq section Date: Tue, 17 Mar 2020 22:44:25 -0700 Message-Id: <20200318054425.111928-1-swboyd@chromium.org> X-Mailer: git-send-email 2.25.1.481.gfbce0eb801-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add the missing word to make this sentence read properly. Signed-off-by: Stephen Boyd --- Documentation/kernel-hacking/locking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst index a8518ac0d31d..9850c1e52607 100644 --- a/Documentation/kernel-hacking/locking.rst +++ b/Documentation/kernel-hacking/locking.rst @@ -263,7 +263,7 @@ by a hardware interrupt on another CPU. This is where interrupts on that cpu, then grab the lock. :c:func:`spin_unlock_irq()` does the reverse. -The irq handler does not to use :c:func:`spin_lock_irq()`, because +The irq handler does not need to use :c:func:`spin_lock_irq()`, because the softirq cannot run while the irq handler is running: it can use :c:func:`spin_lock()`, which is slightly faster. The only exception would be if a different hardware irq handler uses the same lock: base-commit: fb33c6510d5595144d585aa194d377cf74d31911 -- Sent by a computer, using git, on the internet