Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2971925imm; Sun, 5 Aug 2018 17:24:30 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdQKXD387MfFedN1ap5qokoLdSUWUN0XHVz0sHC32d1dPiKKD0XQBIZDQ8RFNJ5XjRkvbH/ X-Received: by 2002:a62:4695:: with SMTP id o21-v6mr14666253pfi.176.1533515070162; Sun, 05 Aug 2018 17:24:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533515070; cv=none; d=google.com; s=arc-20160816; b=ppIZonHfaurzQSY/59Cl+nlvxyAIGXy0MN6oyUcVOFKc4QmlzQzBlopkhof341rvk9 DT0qPanxkRgpfGlHrUOV6XQlEHACCvGWDuliuj9Uv3fslTy1X9apaWBGmT8E1/bDBoFD 98FbTiSXk7vpbrmjelxVYMG5deQy0Zm/0oNxjd908UH1zml6ezWqst7l5Uy6C4xe/a+C Xw0YWAdJBSY9okpRzWNq2z1SdQ2YkfAl4ed3C7G5ZtSJ5lCKyz0bfFZ5lmCXdGjmz/X4 a3XLG+EICz6fsYQClMxWuiPLjoLGB6M01otpfyL975ndrz/h84/M9amt4c4ijppik8mZ yH2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature :arc-authentication-results; bh=IdpQbaQ32i5slcI8UnxKIN+itjJ0QGA9hP7Zha22vzo=; b=sJG0oQS3EelosZm1btuNFwo1g+49U3nBrHfNUt0AVHpti8RIGD0mnbyC6O1MClomR0 XBZhcuMwHw/5gNP6ZxuhZ05P+zwJzLLC2/VU78iSjrLQuE20a1Z8LGZ8ygFZiml0DAZX yjqXnBf0iRrbBMILuUGOnuIpH/fkYyRofGEnabxBhrHSEJRiTOWLs4VAZxH5jEUVsOvy STFxEYLZsE0vX/4wE+TlYZHCg82BD+N9ARqZODyUBY+/umOdbrVeWuU88UQp8PBNtY1C bgaxDRQ7ubRMhPUcPzRALglpdGvVJIMTQOow9aTjqSeibt8YStRP7ov5ukpngUkshSi6 f59A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@tobin.cc header.s=fm3 header.b=B4HT+ulL; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HvcnF+Hs; 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 o14-v6si9015963pll.185.2018.08.05.17.24.15; Sun, 05 Aug 2018 17:24:30 -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; dkim=pass header.i=@tobin.cc header.s=fm3 header.b=B4HT+ulL; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HvcnF+Hs; 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 S1727522AbeHFC3r (ORCPT + 99 others); Sun, 5 Aug 2018 22:29:47 -0400 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:36377 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726870AbeHFC3q (ORCPT ); Sun, 5 Aug 2018 22:29:46 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 5D7CE431; Sun, 5 Aug 2018 20:23:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 05 Aug 2018 20:23:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tobin.cc; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=IdpQbaQ32i5slcI8UnxKIN+itjJ0QGA9hP7Zha22vzo=; b=B4HT+ulL nonvVSAVPQwhjFJm9j+pDQtFeWlHgtcyVN3Tit1ekjpnDBNwRWkcWsoWIxtdhY05 lB+j0YRlElQL3lxVIEImXmv8zaRwZPuHMKkwNJeFsMk6zAFI3ZcoKZpHNxsw51s/ GqgIE0HySQdCTLUUpO0fyIAUXIVSlomraNC0kxXvjNZRjJZxEW6cOSDObjZAo6TT 9PkbmfZUjhi6O0IHS1p6Fs2gFm/9QJGSqwc8/JoYMEzUidc3ozxYAAvyAOxuekLn Dg95iCdOUuxdk+HfKhQHh8RNpMC6mpt4n4IVYF3OO3DDNVYRohS+LRUynL79pIvu 3iY6xe2b4QbmlQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=IdpQbaQ32i5slcI8UnxKIN+itjJ0Q GA9hP7Zha22vzo=; b=HvcnF+HsESAJDSXr1jLierxAcrbHO7J0ssrS9iuqU8kCr z9XLjZ1Kh7R36PmBDscbtqL4zSqR5yDpPaJvJzE8+vcIl7EEKNw+t7dQn+49UuKt HNmETGDy5IwFVBjuIPi+P2gru4eCrT7djvck0HZDrBFcwyKEacUQYoGRAAVa/B58 nn08bPSpj4aJQQrX0e58fF6V6oH2SpNTh/6Cz+gMMXBGXDmunr1rmmNmQrJ7qSdT X88WB0CLBS4hviJ8c2BmskLqdn94ygMLm/X0HAUnyvX4TzGarikdf8iC42tOENdc q2rI+AKk9bVe4pliTIUalyYKAN0ijXPOZ2IzAwYuQ== X-ME-Proxy: X-ME-Sender: Received: from localhost (ppp121-44-251-7.bras2.syd2.internode.on.net [121.44.251.7]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C0E5E455E; Sun, 5 Aug 2018 20:23:16 -0400 (EDT) Date: Mon, 6 Aug 2018 10:23:14 +1000 From: "Tobin C. Harding" To: Daniel Borkmann Cc: Alexei Starovoitov , Jonathan Corbet , "David S. Miller" , linux-doc@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH bpf-next 12/13] docs: net: Fix various minor typos Message-ID: <20180806002314.GK3088@eros> References: <20180801050908.29970-1-me@tobin.cc> <20180801050908.29970-13-me@tobin.cc> <76cf11bc-61b3-8068-5546-79d3ff3a58e9@iogearbox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76cf11bc-61b3-8068-5546-79d3ff3a58e9@iogearbox.net> X-Mailer: Mutt 1.9.4 (2018-02-28) User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 03, 2018 at 10:41:12AM +0200, Daniel Borkmann wrote: > On 08/01/2018 07:09 AM, Tobin C. Harding wrote: > > There are a few minor typos and grammatical issues. We should however > > try to keep the current flavour of the document. > > > > Fix typos and grammar if glaringly required. > > > > Signed-off-by: Tobin C. Harding > > Overall looks good, just some minor nits: > > > Documentation/networking/filter.rst | 65 +++++++++++++++-------------- > > 1 file changed, 33 insertions(+), 32 deletions(-) > > > > diff --git a/Documentation/networking/filter.rst b/Documentation/networking/filter.rst > > index 99dfa74fc4f7..b989a6c882b8 100644 > > --- a/Documentation/networking/filter.rst > > +++ b/Documentation/networking/filter.rst > > @@ -32,10 +32,10 @@ removing the old one and placing your new one in its place, assuming your > > filter has passed the checks, otherwise if it fails the old filter will > > remain on that socket. > > > > -SO_LOCK_FILTER option allows to lock the filter attached to a socket. Once > > -set, a filter cannot be removed or changed. This allows one process to > > +SO_LOCK_FILTER option allows locking of the filter attached to a socket. > > +Once set, a filter cannot be removed or changed. This allows one process to > > setup a socket, attach a filter, lock it then drop privileges and be > > -assured that the filter will be kept until the socket is closed. > > +assured that the filter will be kept until the socket is closed. > > ^-- looks like extra whitespace slipped in? Fixed in the RFC. Thanks for taking the time review. Tobin