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:49:23 -0700 [thread overview]
Message-ID: <4def7caf-6726-e373-181e-4fd698ef5b53@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.
For the changes that are in source code language instead of in comments,
did you re-compile those changes?
>> ----------------------------------------------------------------
>> Kenny Van de Maele (1):
>> fix common spelling mistakes
>
>
more:
drivers/nfc/pn533/pn533.c
@@ -601,7 +601,7 @@ static int pn533_send_sync_complete(struct pn533 *dev, void *_arg,
* as it's been already freed at the beginning of RX path by
* async_complete_cb.
*
- * 3. valid pointer in case of succesfult RX path
+ * 3. valid pointer in case of successfult RX path
*
* A caller has to check a return value with IS_ERR macro. If the test pass,
* the returned pointer is valid.
and:
drivers/scsi/mpt3sas/mpt3sas_scsih.c
@@ -4768,7 +4768,7 @@ _scsih_normalize_sense(char *sense_buffer, struct sense_info *data)
}
/**
- * _scsih_scsi_ioc_info - translated non-succesfull SCSI_IO request
+ * _scsih_scsi_ioc_info - translated non-successfull SCSI_IO request
* @ioc: per adapter object
* @scmd: pointer to scsi command object
* @mpi_reply: reply mf payload returned from firmware
and:
ipc/sem.c
@@ -2092,7 +2092,7 @@ static long do_semtimedop(int semid, struct sembuf __user *tsops,
queue.dupsop = dupsop;
error = perform_atomic_semop(sma, &queue);
- if (error == 0) { /* non-blocking succesfull path */
+ if (error == 0) { /* non-blocking successfull path */
DEFINE_WAKE_Q(wake_q);
/*
eh?:
tools/perf/util/parse-events.c
@@ -767,7 +767,7 @@ split_bpf_config_terms(struct list_head *evt_head_config,
/*
* Currectly, all possible user config term
* belong to bpf object. parse_events__is_hardcoded_term()
- * happends to be a good flag.
+ * happeneds to be a good flag.
*
* See parse_events_config_bpf() and
* config_term_tracepoint().
but once these changes are fixed, overall this is a good set of corrections.
--
~Randy
prev parent reply other threads:[~2019-04-11 15:49 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
2019-04-11 15:49 ` Randy Dunlap [this message]
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=4def7caf-6726-e373-181e-4fd698ef5b53@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®