All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] scripts/spelling.txt: drop "sepc" from the misspelling list
Date: Sun, 19 May 2019 11:24:22 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1905191108180.10723@viisi.sifive.com> (raw)
In-Reply-To: <201b9ab622b8359225f3a3b673a05047ffce5744.camel@perches.com>

On Sat, 18 May 2019, Joe Perches wrote:

> On Sat, 2019-05-18 at 14:00 -0700, Paul Walmsley wrote:
> > The RISC-V architecture has a register named the "Supervisor Exception
> > Program Counter", or "sepc".  This abbreviation triggers
> > checkpatch.pl's misspelling detector, resulting in noise in the
> > checkpatch output.  The risk that this noise could cause more useful
> > warnings to be missed seems to outweigh the harm of an occasional
> > misspelling of "spec".  Thus drop the "sepc" entry from the
> > misspelling list.
> 
> I would agree if you first fixed the existing sepc/spec
> and sepcific/specific typos.
> 
> arch/powerpc/kvm/book3s_xics.c:	 * a pending interrupt, this is a SW error and PAPR sepcifies
> arch/unicore32/include/mach/regs-gpio.h: * Sepcial Voltage Detect Reg GPIO_GPIR.
> drivers/scsi/lpfc/lpfc_init.c:		/* Stop any OneConnect device sepcific driver timers */
> drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c:* OverView:	Read "sepcific bits" from BB register
> drivers/net/wireless/realtek/rtlwifi/wifi.h:/* Ref: 802.11i sepc D10.0 7.3.2.25.1

Your agreement shouldn't be needed for the patch I sent.


- Paul

  reply	other threads:[~2019-05-19 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 21:00 [PATCH] scripts/spelling.txt: drop "sepc" from the misspelling list Paul Walmsley
2019-05-19  5:07 ` Joe Perches
2019-05-19 18:24   ` Paul Walmsley [this message]
2019-05-22  0:14     ` Andrew Morton
2019-05-22  4:47       ` Paul Walmsley
2019-05-22  5:34         ` Joe Perches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.9999.1905191108180.10723@viisi.sifive.com \
    --to=paul.walmsley@sifive.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.