All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] treewide: fix a bunch of typos
Date: Thu, 11 Aug 2016 22:01:04 +0900	[thread overview]
Message-ID: <CAK7LNATiEk3pvnsqpkPogNZK8Of7p0shV_xUSye=dO63xLZR4Q@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwbE0JP8wbZM6hTpwSGRyQNwkC8pGR6XH7cidni8MZ9pg@mail.gmail.com>

Hi Linus,


2016-08-09 3:03 GMT+09:00 Linus Torvalds <torvalds@linux-foundation.org>:
> On Sun, Aug 7, 2016 at 6:56 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>>
>> Sorry for chiming in at the last minute of the MW.
>>
>> I am not sure if you like this, but here is a bunch of typo fixes.
>> All of them are very trivial, but I am afraid this treewide patch is
>> conflict-prone.
>
> The worst part about patches like this is that they are a bitch to
> check. They're huge and I haev a hard time verifying that the patch
> does *exactly* what described, and there isn't something else in there
> hiding.
>
> I assume this patch was generated with a script anyway? I'd much
> rather just re-run the script itself on my tree, and that would make
> me feel less like I had to review it.
>
> So would you mind just sending me the sed-script (or whatever you used) instead?

First, I apologize for disturbing you just before the rc1 release.

This patch was generated by a sed-script and verified by my eyes,
but I did not keep the script.

It was difficult for me to write a sed script to do a perfect job.
So, I did it incrementally; run a small sed script, and then discard
unwanted/false-positive conversions by "git checkout -p".  I repeated
this process several times to build up this patch.

If you prefer a sed-script, I will give it a try once again, but it
will be impossible to produce the same result.

This patch also includes several manual fixups.

For example, "explict" was replaced with "explicit" by the script in
the following hunk, but also I noticed and fixed "a" to "an" manually.

- *  -In TLB Flush operations (Metal Fix MMU) there is a explict command to
+ *  -In TLB Flush operations (Metal Fix MMU) there is an explicit command to



Moreover, I noticed many typos in code as well as comments.

For example, I wondered if I should fix the following macro
in drivers/net/wireless/realtek/rtlwifi/wifi.h .
(rename "N_BYTE_ALIGMENT" to "N_BYTE_ALIGNMENT")

  #define N_BYTE_ALIGMENT(__value, __aligment) ((__aligment == 1) ? \
       (__value) : (((__value + __aligment - 1) / __aligment) * __aligment))


Finally, I decided to be defensive, and
I drop all changes in code by "git checkout -p".


So, if you run a sed-script in your tree,
perhaps you may want to check the result by your eyes.


Now this patch was checked by three people
(me, Randy Dunlap, Geert Uytterhoeven).

Randy pointed out some parts should be fixed.

I am happy to send v2 if desired.
If you prefer (and more trust) a sed script, I will my best to write a one.


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2016-08-11 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07 13:56 [PATCH] treewide: fix a bunch of typos Masahiro Yamada
2016-08-08  4:09 ` [PATCH] treewide: fix a bunch of typos (Documentation/) Randy Dunlap
2016-08-08  4:50 ` [PATCH] treewide: fix a bunch of typos (part 2) Randy Dunlap
2016-08-08  5:20   ` Masahiro Yamada
2016-08-08 14:38     ` Randy Dunlap
2016-08-08  9:40 ` [PATCH] treewide: fix a bunch of typos Geert Uytterhoeven
2016-08-08 18:03 ` Linus Torvalds
2016-08-11 13:01   ` Masahiro Yamada [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='CAK7LNATiEk3pvnsqpkPogNZK8Of7p0shV_xUSye=dO63xLZR4Q@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.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.