Received: by 10.213.65.68 with SMTP id h4csp812618imn; Fri, 23 Mar 2018 17:27:46 -0700 (PDT) X-Google-Smtp-Source: AG47ELuKfqvG80QvadDsvhwLxNsWlvJ6ZuQw3m0p+XxifbF5lAVq4oI16nFWSzJrjsX1ingoJ0MQ X-Received: by 10.101.81.8 with SMTP id f8mr22256590pgq.13.1521851266891; Fri, 23 Mar 2018 17:27:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521851266; cv=none; d=google.com; s=arc-20160816; b=oP4fEdoVbPipuRMjtW8b/wiWSzSYFFGySxba2CEeVKdqKK5mGSvm+FXnQGNG0hXc0n m+ef8olpgZNJjP64VF2Pko/xoXSoxuAh3ftFtypcSAbOIVqi2JKHlrSx1ayVi9pldq8p 2dLaO2nKGHoZzCHadlPRygqCpJ3tMRV15pRlInb6ByZeZkuWGnX+byqcaZQt8EP4eyT/ QD9zdDEiyyqamX83HO2WQw7sJoVtSg+c2GFhfB+l3vez5HqHdYcT0D76On2/AjM/lqVx L71a7yqPjT+QF/HgoW+K2/BMCt/rkoAVae//vBXF/IIcdqpx979aFXk141bNPTiP8cOp GNmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:message-id:date:cc:to:from :arc-authentication-results; bh=xhmWzcLlUA0RptWl3pbzXzyGWY/GEpQXAzRioGokfoQ=; b=wuuEw8UCaZmHK6PL7SIPUnFFyN2HKT2ZwQ99QdlCCggLDBc4TzZrHBonXNA/Ld08CV NCP/Mw3WOjlM2CX9v+5jRpRoGbcD7RQq4cZqsK2eSKnoiiXwxPOv0dpQmSZzhQ3EyOq7 Wa3fS+DN9A1H0BKI+M3dHPbB+mqyN7cKzIHNCqlmqL3iLBvzsUjZBG8eEo8DZ//2uit7 BehKUJdHqWmpHtENVNVTrjiZcVwBLO0sSBMu/HdoUhBzcRDf3rJgRMimsFAaTer4Ek6O jqIG5K5AfGh9iWaMVWDReOR//AMNZY7DEqll5DRM0Eiyc/bUGNLTiNoVFk7aw//sEs+2 8zig== 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 63si7474732pff.224.2018.03.23.17.27.32; Fri, 23 Mar 2018 17:27:46 -0700 (PDT) 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 S1751938AbeCXA0n (ORCPT + 99 others); Fri, 23 Mar 2018 20:26:43 -0400 Received: from mail.CARNet.hr ([161.53.123.6]:52578 "EHLO mail.carnet.hr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751632AbeCXA0n (ORCPT ); Fri, 23 Mar 2018 20:26:43 -0400 Received: from cnzgrivvl-t440p.carpriv.carnet.hr ([161.53.12.131]:46512 helo=gavran.carpriv.carnet.hr) by mail.carnet.hr with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ezX15-0004da-MY; Sat, 24 Mar 2018 01:26:40 +0100 Received: by gavran.carpriv.carnet.hr (Postfix, from userid 1000) id 564FC25055; Sat, 24 Mar 2018 01:26:39 +0100 (CET) From: Valentin Vidic To: Stefani Seibold Cc: Mauro Carvalho Chehab , Christophe JAILLET , Jiri Kosina , Sean Young , linux-kernel@vger.kernel.org, Valentin Vidic Date: Sat, 24 Mar 2018 01:26:30 +0100 Message-Id: <20180324002630.13046-1-Valentin.Vidic@CARNet.hr> X-Mailer: git-send-email 2.16.2 X-SA-Exim-Connect-IP: 161.53.12.131 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on rigel.CARNet.hr X-Spam-Level: X-Spam-Status: No, score=-2.9 required=10.0 tests=ALL_TRUSTED,BAYES_00, T_RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=ham version=3.3.2 Subject: [PATCH] kfifo: fix comment X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Cleanup unusual formatting in the note about locking. Signed-off-by: Valentin Vidic --- include/linux/kfifo.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/linux/kfifo.h b/include/linux/kfifo.h index e251533a5939..89fc8dc7bf38 100644 --- a/include/linux/kfifo.h +++ b/include/linux/kfifo.h @@ -41,11 +41,11 @@ */ /* - * Note about locking : There is no locking required until only * one reader - * and one writer is using the fifo and no kfifo_reset() will be * called - * kfifo_reset_out() can be safely used, until it will be only called + * Note about locking: There is no locking required until only one reader + * and one writer is using the fifo and no kfifo_reset() will be called. + * kfifo_reset_out() can be safely used, until it will be only called * in the reader thread. - * For multiple writer and one reader there is only a need to lock the writer. + * For multiple writer and one reader there is only a need to lock the writer. * And vice versa for only one writer and multiple reader there is only a need * to lock the reader. */ -- 2.16.2