All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Michael Opdenacker" <michael.opdenacker@free-electrons.com>,
	trivial@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the "
Date: Tue, 12 Nov 2013 09:32:23 +0100	[thread overview]
Message-ID: <5281E797.9030101@broadcom.com> (raw)
In-Reply-To: <1384233016-15188-1-git-send-email-michael.opdenacker@free-electrons.com>

On 11/12/2013 06:10 AM, Michael Opdenacker wrote:
> Fix all occurrences of "the the " in the source code,
> comments and documentation.
>
> The replacement couldn't be automated because sometimes
> the first "the" was meant to be another word.
>
> Example: "according the the"
> meaning: "according to the"
>
> Note that I sometimes took the opportunity to fix
> other spelling issues or typos in the same sentences.
> I also fixed a few checkpatch errors in the same
> lines.
>
> This is an update to the patch sent on Sep. 12, 2013

Better put this kind of info below the signed-off-by line. Or even 
better use the message-id of that patch in the 'In-Reply-To:' field that 
git-send-email prompts for.

For driver change mentioned below:
Acked-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
---
so here: 'This is an update to the patch sent on Sep. 12, 2013'
> ---
>   drivers/net/wireless/brcm80211/brcmsmac/main.c                 | 2 +-



  reply	other threads:[~2013-11-12  8:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  5:10 [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the " Michael Opdenacker
2013-11-12  8:32 ` Arend van Spriel [this message]
2013-11-13  9:27   ` Michael Opdenacker
2013-12-09 10:36   ` [PATCH][RESEND] [TRIVIAL] " Michael Opdenacker
2014-03-05  5:52     ` [PATCH] [RESEND][TRIVIAL] " Michael Opdenacker
2014-03-05  5:55       ` Michael Opdenacker
2014-03-11 12:25         ` Michael Opdenacker
2014-03-11 12:30           ` Michael Opdenacker
2014-10-01  9:53       ` Michael Opdenacker
2014-10-01 13:32         ` Joe Perches
2014-10-01 19:49           ` Michael Opdenacker
2014-10-01 19:54             ` Michael Opdenacker
2014-10-02 17:25               ` Randy Dunlap
2014-10-02 19:18                 ` Michael Opdenacker
2014-10-02 19:24                   ` Michael Opdenacker
2014-10-02 20:00                     ` Randy Dunlap
2014-10-02 20:06                       ` Joe Perches
2014-10-02 20:11                         ` Michael Opdenacker
2014-10-02 20:13                           ` Michael Opdenacker
2014-10-02 20:15                             ` Michael Opdenacker
2014-10-02 22:37                               ` Eduardo Valentin
2014-10-16 12:35                                 ` Michael Opdenacker
2014-10-16 12:39                                   ` Michael Opdenacker
2014-10-16 19:38                                   ` Michael Opdenacker
2014-10-16 19:42                                     ` Michael Opdenacker
2015-03-27  1:55                                       ` Michael Opdenacker
2015-03-27  2:16                                         ` Michael Opdenacker
2015-03-27  9:34                                           ` Jiri Kosina
2015-04-20  4:55                                             ` Michael Opdenacker
2015-04-20  5:02                                               ` Michael Opdenacker
2015-03-27  2:23                                         ` Joe Perches
2015-03-27  2:52                                           ` Michael Opdenacker
2015-03-27  2:55                                             ` Michael Opdenacker
2014-10-02 20:07                       ` Michael Opdenacker
2014-10-02 20:07                   ` Michael Opdenacker

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=5281E797.9030101@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=trivial@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.