Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp468732yba; Fri, 3 May 2019 05:24:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqx/H3HSyHGiB6fHoVgiThewpKgbazuxwgtjVBudUEUK5Mz/il4gwFc/tNxh0AOG8oWgt9mZ X-Received: by 2002:aa7:9afc:: with SMTP id y28mr10380993pfp.101.1556886282991; Fri, 03 May 2019 05:24:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556886282; cv=none; d=google.com; s=arc-20160816; b=0LIiJI+lsCSzacOb51ryhInGQozpizz/56gUOgB3pCrMeqUfgEcJkA2VB5x1ulnvrx bWmTcKqBUua9KrCSGGu/jtRjJ1Ph2iUM6fdiao5kw+bCPYqmUDiyRxk/5+cnEbbAz+1R tMZSnwov6jzbK/4JGdzG8zcbc4rU/EzmqFrCUzkmOh249q2ZamMBAFaMXJiLVmit94j9 RsLR3asL1kgum/w7W3rrdcyyM7B7xNkT+5O6W7KAD9vPvcWZ4FHmof6bN9bB+FZTC0BU DPhfK8KaCzYK4uQ7ZSRCvDJG2WZdnY6InSCO45MBiIyqzyq2BqJPcpe9uL/lrkvRRYmt 6oDQ== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=PKr8frViZzfxVghFRyuvPdarSHRRayYkCBzO4X6Ad+E=; b=gQeXT85nVJnnplC2B87fpNj/cGPj5U8yZEeXr9VIPXl1mY992WiJ8cNzXGgZNxxaAh 7TKoqHoSeCsEslwZQDyi0Q2lvBjlR6oRdj97nt0x7dlCqxv6iwhRf5s9W39Nb6P5CdCj RDsneUesREpPeAC8lJHIa/jG4czB3f/rNK2AGfBdru3inBJOKAfiNDAihpf4z/BowzPh vvHq7YXcS+fIemETWf5ragXTkctme4LsZ7G2Paej6MFfpNXgOZuVIn1uhM1Za/pCEZqT BTNWU/wBt8bLtHQKRyiSazIF/gtaqa8IfUXAxHwOynd4ho3zDKaFB7jCd31H/Cp4+DI2 k6VA== 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 o3si2241887pld.425.2019.05.03.05.24.26; Fri, 03 May 2019 05:24:42 -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 S1727768AbfECMXZ (ORCPT + 99 others); Fri, 3 May 2019 08:23:25 -0400 Received: from ms.lwn.net ([45.79.88.28]:47944 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbfECMXZ (ORCPT ); Fri, 3 May 2019 08:23:25 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id DAF647DE; Fri, 3 May 2019 12:23:22 +0000 (UTC) Date: Fri, 3 May 2019 06:23:20 -0600 From: Jonathan Corbet To: Randy Dunlap Cc: "Tobin C. Harding" , Johan Hovold , "Tobin C. Harding" , Josh Poimboeuf , Jiri Kosina , Miroslav Benes , Petr Mladek , Greg Kroah-Hartman , "Rafael J. Wysocki" , Joe Lawrence , live-patching@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 3/5] kobject: Fix kernel-doc comment first line Message-ID: <20190503062320.62849fd4@lwn.net> In-Reply-To: <8e237ab7-681b-dccf-792f-264e3f6fcd2d@infradead.org> References: <20190502023142.20139-1-tobin@kernel.org> <20190502023142.20139-4-tobin@kernel.org> <20190502073823.GQ26546@localhost> <20190502082539.GB18363@eros.localdomain> <20190502083922.GR26546@localhost> <20190503014015.GC7416@eros.localdomain> <8e237ab7-681b-dccf-792f-264e3f6fcd2d@infradead.org> Organization: LWN.net X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2 May 2019 18:46:16 -0700 Randy Dunlap wrote: > I have seen this discussion before also. And sometimes it is not even > a discussion -- it's more of an edict. To which I object/disagree. > The current (or past) comment style is perfectly fine IMO. > No caps needed. No ending '.' needed. For however much this matters...I really don't see that there needs to be a rule one way or the other on this; the documentation serves its purpose either way. I guess I see it like "British or American spelling"; there's nothing to drive a conversion in either direction. jon