From: Randy Dunlap <rdunlap@infradead.org>
To: Kenny Van de Maele <kenny.vandemaele@inuits.eu>,
torvalds@linux-foundation.org
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] <global> global spelling corrections for v5.1.0-rc5
Date: Thu, 11 Apr 2019 08:39:33 -0700 [thread overview]
Message-ID: <1a423b4e-16e7-8884-54ef-50833d472ca4@infradead.org> (raw)
In-Reply-To: <0885bbf9-ccb1-280e-dde1-ffa40282df09@infradead.org>
On 4/11/19 7:58 AM, Randy Dunlap wrote:
> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>> are available in the Git repository at:
>>
>> git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>> spelling-fixes-5.1.0-rc5
>>
>> for you to fetch changes up to
>> 6ee0055f3414a64133228e82004ea60d0e659d6d:
>>
>> fix common spelling mistakes (2019-04-11 10:22:24 +0200)
>>
>> ----------------------------------------------------------------
>> This PR contains a set of global spelling fixes of commonly miss-
>> spelled
>
> misspelled
>
>
> Is there a way for me to review the diff on github?
>
> thanks.
>
>
>> words. Mostly documentation and comments were impacted, but a few lines
>> of code were affected as well.
>>
>> ----------------------------------------------------------------
>> Kenny Van de Maele (1):
>> fix common spelling mistakes
>
>
recheck:
drivers/net/wireless/ralink/rt2x00/rt2x00link.c
@@ -203,7 +203,7 @@ void rt2x00link_update_stats(struct rt2x00_dev *rt2x00dev,
return;
/*
- * Frame was received successfully since non-succesfull
+ * Frame was received successfully since non-successfull
* frames would have been dropped by the hardware.
*/
qual->rx_success++;
--
~Randy
next prev parent reply other threads:[~2019-04-11 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 9:12 Kenny Van de Maele
2019-04-11 14:58 ` Randy Dunlap
2019-04-11 15:00 ` Kenny Van de Maele
2019-04-11 15:29 ` Randy Dunlap
2019-04-11 15:37 ` Randy Dunlap
2019-04-11 15:39 ` Randy Dunlap [this message]
2019-04-11 15:49 ` Randy Dunlap
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=1a423b4e-16e7-8884-54ef-50833d472ca4@infradead.org \
--to=rdunlap@infradead.org \
--cc=kenny.vandemaele@inuits.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®