linux-kernel - Re: [GIT PULL] <global> global spelling corrections for v5.1.0-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4def7caf-6726-e373-181e-4fd698ef5b53@infradead.org>
Date:   Thu, 11 Apr 2019 08:49:23 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Kenny Van de Maele <kenny.vandemaele@...its.eu>,
        torvalds@...ux-foundation.org
Cc:     torvalds@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] <global> global spelling corrections for v5.1.0-rc5

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