From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: trivial@kernel.org
Cc: Eduardo Valentin <edubezval@gmail.com>,
rdunlap@infradead.org, joe@perches.com,
akpm@linux-foundation.org, arend@broadcom.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the "
Date: Thu, 16 Oct 2014 21:38:05 +0200 [thread overview]
Message-ID: <54401E9D.4050707@free-electrons.com> (raw)
In-Reply-To: <543FBB95.9010209@free-electrons.com>
On 10/16/2014 02:35 PM, Michael Opdenacker wrote:
> Greetings,
>
> On 10/03/2014 12:37 AM, Eduardo Valentin wrote:
>
>> On Tmon behalf:
>>
>> Acked-by: Eduardo Valentin <edubezval@gmail.com>
> Any chance to get this perged before the end of the current merge window
> (Linus said it would last until sometime next week)? I'm posting a new
> update with fixes for new issues that accumulated... Otherwise, there
> will be even more the next time, and current reviews may get obsolete.
>
> And I'd also hate to have to send commits to individual maintainers,
> polluting the history tree with loads of commits for the same trivial
> change...
As I was advised, I will resent once more and copy Linus this time, in
case he is available to help with this ever-growing treewide patch.
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
next prev parent reply other threads:[~2014-10-16 19:38 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
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 [this message]
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=54401E9D.4050707@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=akpm@linux-foundation.org \
--cc=arend@broadcom.com \
--cc=edubezval@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox