Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2900679ybd; Mon, 24 Jun 2019 15:01:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxtbfYBMx660c856QxGKG9hfs7enUSMktzMhJ7wC+iW7xmvylauNDaz4B1voAaPXueXaof X-Received: by 2002:a63:1f23:: with SMTP id f35mr35548570pgf.160.1561413710020; Mon, 24 Jun 2019 15:01:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561413710; cv=none; d=google.com; s=arc-20160816; b=Q03I3U4kn1LSZGwGJp+mdiP1WybAYzjX85hwWyMIC47WXwmzlt8pdMa596l53xyJMH riaeJNvFgVwr/z2UblzKXKBZCpylaa81K2aWZe6+hUPpMnuPR3BV0WPT+32DYlxKt/I4 b12VBPuSes9s9HZELbu/LZ29lK9MoaoZM1/+uyG5n3JWB5w4ZWc5xDZ7M46Ww4ZpHMuF NxkT+JHJRv9kPHbQzHZI0esB6BoOMCX8HOK5TYmTUqedkvgYsYlZphsPRxl0296JGcFI 7tuhIp/C70O8erakadP5+ECglKAfNKF1YAFwA9qtqWxTvXfy8ZhY1GaG/3xyo9zlwFaW 5sRw== 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 :user-agent:references:in-reply-to:date:to:from:subject:message-id; bh=M2tZ++4oS0YRW7zYZzSJ9RxM5g9SyXzbnLW8wiUEA8E=; b=bEDyQ+ALDp3N6eon0QprIOJwZwB09MMzhIbY2Q6pUpE7ZHcULfNOADLXk3p2C4LQHp yh/WByvONZA2M5KzQPMt/EbhOUZ3hzap3BhPPzuJg7z1iEn3VRle89QsjTqJ3N9qJr4J B9OUzK7DGNf0D5RQlVquYyLlmdtbDsbH/Icf2KaWhshg4FF5cWq2JEuvSXKGHXgmYVbK qKS5g09xkyr2GBZwtIUIdLJjZ4T6J95zbILCjAtu4eN88UDlVicjmyxZ8AEn3mdXtcRb bBA60RaEAFd1QL8kOQCiNAcgbXe8eDp/a1vyQMDJ1cGAFvlFHxeBv1q5CKKPUrfVb2gF gnWw== 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 g98si657528pje.92.2019.06.24.15.01.33; Mon, 24 Jun 2019 15:01:50 -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 S1731749AbfFXU3s (ORCPT + 99 others); Mon, 24 Jun 2019 16:29:48 -0400 Received: from smtprelay0192.hostedemail.com ([216.40.44.192]:38887 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726393AbfFXU3s (ORCPT ); Mon, 24 Jun 2019 16:29:48 -0400 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id 586A3182CED2A; Mon, 24 Jun 2019 20:29:46 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::,RULES_HIT:41:355:379:599:800:960:967:973:982:988:989:1260:1277:1311:1313:1314:1345:1359:1381:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2393:2525:2559:2563:2682:2685:2691:2693:2828:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3354:3622:3865:3866:3867:3868:3870:3871:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4321:5007:6119:6691:7903:7904:9025:10004:10400:10848:11232:11658:11914:12043:12048:12297:12555:12663:12740:12760:12895:12986:13069:13071:13311:13357:13439:14180:14181:14659:14721:21060:21080:21433:21451:21611:21627:21811:30054:30091,0,RBL:23.242.196.136:@perches.com:.lbl8.mailshell.net-62.8.0.180 64.201.201.201,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:neutral,Custom_rules:0:0:0,LFtime:29,LUA_SUMMARY:none X-HE-Tag: road72_1ae72be6d3a1a X-Filterd-Recvd-Size: 3216 Received: from XPS-9350.home (cpe-23-242-196-136.socal.res.rr.com [23.242.196.136]) (Authenticated sender: joe@perches.com) by omf12.hostedemail.com (Postfix) with ESMTPA; Mon, 24 Jun 2019 20:29:44 +0000 (UTC) Message-ID: <977bc7c484ef55ff78de51d7555afcc3c3350b1e.camel@perches.com> Subject: Re: [PATCH 0/3] Clean up crypto documentation From: Joe Perches To: Gary R Hook , "Hook, Gary" , "herbert@gondor.apana.org.au" , "corbet@lwn.net" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-crypto@vger.kernel.org" , "davem@davemloft.net" Date: Mon, 24 Jun 2019 13:29:42 -0700 In-Reply-To: References: <156140322426.29777.8610751479936722967.stgit@taos> <23a5979082c89d7028409ad9ae082840411e1ca6.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.30.5-0ubuntu0.18.10.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2019-06-24 at 20:06 +0000, Gary R Hook wrote: Hi Gary. > On 6/24/19 2:30 PM, Joe Perches wrote: > > On Mon, 2019-06-24 at 19:07 +0000, Hook, Gary wrote: > > > Tidy up the crypto documentation by filling in some variable > > > descriptions, make some grammatical corrections, and enhance > > > formatting. > > > > While this seems generally OK, please try not to make the > > readability of the source _text_ less intelligible just > > to enhance the output formatting of the html. > > > > e.g.: > > > > Unnecessary blank lines separating function descriptions > > Removing space alignment from bullet point descriptions > > Apologies. I generally consider white space a Good Thing, > but will take your note and not do that. The blank lines I > added do not affect the output, so I should not have done > that. > > Also, I turned sentences into bulleted lists here, so I'm not > clear on whether that was a Bad Thing or not. To me, using bulleted lists are not a bad thing at all but are quite the opposite for humans to read. > Seems more legible > to me all the way around, but I clearly could be incorrect. Not at all. > I agree that mucking with alignment is a bad thing, and would not > intentionally do so. That said, if you would please elaborate on > any mistakes I've made? > > Finally, would you prefer a v2 of the patch set? Happy to do > whatever is preferred, of course. Whatever Jonathan decides is fine with me. Mine was just a plea to avoid unnecessarily making the source text harder to read as that's what I mostly use. I don't know if this extension is valid yet, but I believe just using () is more readable as text than ```` or :c:func:`` https://lore.kernel.org/lkml/20190425200125.12302-1-corbet@lwn.net/T/ I prefer the automatic approach over the manual marking of functions as ideally sphinx formatting should not overly impact the source text.