Received: by 10.223.185.116 with SMTP id b49csp2894661wrg; Sun, 18 Feb 2018 09:02:11 -0800 (PST) X-Google-Smtp-Source: AH8x224Irzjys6Hd9/f5LWoN4xUlyhQ12ChkzOGIlurTNAsl3+8XNIKsgS7KTEo6bhDK+1NoEvla X-Received: by 2002:a17:902:4222:: with SMTP id g31-v6mr11454413pld.335.1518973331309; Sun, 18 Feb 2018 09:02:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518973331; cv=none; d=google.com; s=arc-20160816; b=MN/EukbWLY+0Td4Xc11r6Wgg6ryR5EFnoyTa7Q57pLZnvcqSd3qvQodA3MVlhsuXJ+ kfp9cyjlZ+M7iG+4+ry4rFIwvJQ04UuqrqqOQ+PbGRkSun3moBXnUW56vgZjPGrYllPn kGIwaiRniYwRjYc7Pfkobvw9lB+YX3iWQNLY20IqE4I/hpcPvadLZfnARkZ42y+W7fQS vF4QGPSx0u9Kc1YYmHWsX4KYJyLILiE15HTbo9Usv5SJq82CoktuIm3T57DgDU6L3y2+ /xbXxkPiRfvjIMQazBkwMwZRJd0LaIAphYmo5eg/rhU2q2F04bMwQLfg7ACk8RzD8fzG NsFw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:dkim-signature :arc-authentication-results; bh=hYirmWfQvQ+RMuvsF/VMRk0O3+FIa2JKxTv3No6CWPQ=; b=yiaH4RG0/VfUhoz8wM+G76QGdnwdb3abKJBv408zs5fVdHko2k/kodvykjWae/S3qs HI5yFvCj/rBHnUJKONSp+EtAG/48bpZy+fEheuUgg74izCE0EDPWL4Xui1FbsItxJmHN pK1lsTxSCV7GD4Nc098xQ8AHpb7QjVtPl8GRsOL2N+BZMQU31hKPnnnF239hfBWGhdin 2HrVIl/W9jpoueEBn8T+hMCmR8aaj9OjSBTBTcSUmGTMIO3+bABOw04EklwXUctH5yg5 bi6+ppBhjwIiWj5y7OG/C/bYYzY6rc005J8CQORT0ckui7ULsftl44mpFGDBk47JBF1S qA0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=qXUWuN5I; 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 u77si2703790pfd.165.2018.02.18.09.01.44; Sun, 18 Feb 2018 09:02:11 -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; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=qXUWuN5I; 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 S1751456AbeBRRA3 (ORCPT + 99 others); Sun, 18 Feb 2018 12:00:29 -0500 Received: from merlin.infradead.org ([205.233.59.134]:39502 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbeBRRA2 (ORCPT ); Sun, 18 Feb 2018 12:00:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=hYirmWfQvQ+RMuvsF/VMRk0O3+FIa2JKxTv3No6CWPQ=; b=qXUWuN5IJvImpDKQd6m5ctgNE6 czhC2sH/RmtYWYf4RC3vzBFo3E5cmuwZafqcevo8soAMQtL3UjXEgTENXO1wbJA+vu2NwU6fzU6OF 85C7CleQyQPudx+OTqZ+1SyvVAlaXCxP2/Ndamjg99xf1uxV4vU5aNGEvGNMwHXU2+AHVZI34xg+l Yf6mueXckvuQvJsxWFKMtF3vEiJNYZd1ijBFwDbC5I5fwzpqUxa8YmqDZpxDbGB30rJ1K+PKnF1Fp 0/D3BEP4Ht3wDG6g8e5Sl6OQ93dB5Fe2XKvyzwd96sK8mdPt4MPQWMYx7CtUBInasmj6TROI8QiiT +jngh6rw==; Received: from static-50-53-52-16.bvtn.or.frontiernet.net ([50.53.52.16] helo=midway.dunlab) by merlin.infradead.org with esmtpsa (Exim 4.89 #1 (Red Hat Linux)) id 1enSKA-0007Ry-IB; Sun, 18 Feb 2018 17:00:27 +0000 Subject: Re: Seeking guidance on spelling fixes To: David Frey , linux kernel References: <7912182.YNFVRYok70@roach> From: Randy Dunlap Message-ID: Date: Sun, 18 Feb 2018 09:00:25 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <7912182.YNFVRYok70@roach> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/18/2018 07:34 AM, David Frey wrote: > I noticed a common spelling mistake in some Linux kernel code that I was > reading the other day and it made me wonder how prevalent common spelling > mistakes are in the kernel. I did some grepping and it seems that there > are a large number of spelling mistakes. I did a bit of searching and I > found (http://www.kegel.com/kerspell/) which includes some comments/tools > relating to spelling and the Linux kernel. > > I have gone ahead and corrected about 100 total instances based on 25 > common misspellings. There are many, many more common misspellings that I > could check, but I don't want to sink more time into this if the changes > won't be accepted. > > Is this type of change likely to be accepted? Right now I am making > individual git commits for each correction. For example "aditional -> > additional". I figured that it would be easier to review the list of > replacements rather than a mega-patch which fixes many different errors. > This way if any of the changes are controversial, I can easily rebase them > out. > > I am trying to only correct true misspellings. I'm not trying to choose > the "most correct" spelling for cases where there are acceptable alternate > spellings. > > I've pushed the changes I have made so far to a "spelling_fixes" branch > here: https://github.com/dpfrey/linux/commits/spelling_fixes just in case > there is any question about what I am doing based on the above description. > > Just to be clear, I'm not trying to get this portion of the work merged at > this point. I'm trying to get a feel for whether I should keep working on > this. I can't answer for others, of course, but fixing spelling in user-visible messages will usually be accepted/merged (e.g., error messages or Kconfig help text). I looked at a few of the commits and they are fixes in comments. I would accept them, but I'm not a maintainer, just a contributor. thanks, -- ~Randy