Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2076198imj; Fri, 8 Feb 2019 12:09:00 -0800 (PST) X-Google-Smtp-Source: AHgI3Ib+SPHIccK3HtstOSAzS+7W2se8UM86omap2Kqjznj87Rl41PaG6PuKdegLoUwNLz6XYxO3 X-Received: by 2002:a63:d347:: with SMTP id u7mr6067072pgi.383.1549656540234; Fri, 08 Feb 2019 12:09:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549656540; cv=none; d=google.com; s=arc-20160816; b=nFt/ZwL4miNT1w9B7y6mjD/LuIdrlfa8FbOVGhuOOnOmtZi5E4QMpn4Ceb+yReEeJJ mTK1jjZLqu20kdPfs+/LgQunclDAKGAmWCJ9EKHLWfHEzTrJ91B2e0+aBFG1rVkhoM5b W35JKGJXKW8J4T/GS1lhbmAt57b1IquBMUSQSka9qZ3i5N844k7MIODVewNtbi647njP JcyIh3c2cWp/pgAxF2qLC69/i/m2+dLrsBiZWOTa9k5lv4wMeIw/vlK+AWnJGBtEC71h 4hlseZ7kWz/3XbtWCb3Rz8/8STR2nnbxzn5GT6XwgS6uizuyNzB69QVsym8VqKCnTT8c jhFA== 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=rfZ3/g6FpzDAx8nM96brS73qjRTmo3kfgFTbq/vI8nA=; b=GYgSaz3G3Ok3312w7URduUiz1w7JcYfcpRz+3n7oEWrvR09ysN6GNcPbOu7veUI2vq 8ZkrnIWw/fQgRnBS+4POcWOj65jX/4OGJ28aWo2d+ijJI5KKoxb65LrPj3aL2C1b++rF QuUbILiUxdBoTnT1hCvK4iP1cKVsBG+Jvov3NjJI8u3AK7+xLNznHLy9XK0jUFw8c+Ip 0oKDkd5owzcMJC1lN6ZMnXvpFOUA6LtQ1ZhMxlzYfovC8Z+wlOb7o7KsrcvoOVQFsVQ4 DYWbCV+Qjk6wCNdsOVvGxiGyEMNF/2xW+5X0s9LljaWNvpBfW2DFWY6SO78yMtJAR+Ic 2+lQ== 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 3si3198263pla.240.2019.02.08.12.08.44; Fri, 08 Feb 2019 12:09:00 -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 S1727450AbfBHUIQ (ORCPT + 99 others); Fri, 8 Feb 2019 15:08:16 -0500 Received: from ms.lwn.net ([45.79.88.28]:56324 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726211AbfBHUIP (ORCPT ); Fri, 8 Feb 2019 15:08:15 -0500 Received: from lwn.net (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 381392CD; Fri, 8 Feb 2019 20:08:15 +0000 (UTC) Date: Fri, 8 Feb 2019 13:08:14 -0700 From: Jonathan Corbet To: Frank Rowand Cc: Matthew Wilcox , Mauro Carvalho Chehab , Mike Rapoport , Joris Gutjahr , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] docs: kernel-doc: typo "documentaion" Message-ID: <20190208130814.3d1534cd@lwn.net> In-Reply-To: <9dc7fd5f-3ed6-f36d-5b84-8fcd3c477181@gmail.com> References: <1549058656-11119-1-git-send-email-frowand.list@gmail.com> <20190202205620.GA13285@bombadil.infradead.org> <9dc7fd5f-3ed6-f36d-5b84-8fcd3c477181@gmail.com> Organization: LWN.net 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 Mon, 4 Feb 2019 16:29:31 -0800 Frank Rowand wrote: > On 2/2/19 12:56 PM, Matthew Wilcox wrote: > > On Fri, Feb 01, 2019 at 02:04:16PM -0800, frowand.list@gmail.com wrote: > >> Include documentation for each *function* in *source*. > >> - If no *function* if specified, the documentaion for all functions > >> + If no *function* if specified, the documentation for all functions > >> and types in the *source* will be included. > > > > Could you fix the if/is mistake while you're at it? > > > > > Jon, > > Since you already accepted the patch, is it easy for you to revert the > patch and apply a v2 with the change Mathew pointed out? If so, I will > do a v2. How about you just send another with the second fix? Seems just as easy in the end... Thanks, jon