From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: edubezval@gmail.com, rdunlap@infradead.org, joe@perches.com,
akpm@linux-foundation.org, arend@broadcom.com,
gregkh@linuxfoundation.org, torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the "
Date: Thu, 26 Mar 2015 19:16:08 -0700 [thread overview]
Message-ID: <5514BD68.4000605@free-electrons.com> (raw)
In-Reply-To: <1427421323-29464-1-git-send-email-michael.opdenacker@free-electrons.com>
On 03/26/2015 06:55 PM, Michael Opdenacker wrote:
> 222 files changed, 493 insertions(+), 258 deletions(-)
Is this patch getting too big (and getting bigger and bigger) to be ever
merged?
Unless you tell me otherwise, I'm thinking about splitting it into
several patches, one for each subsystem. That would unnecessarily
increase the number of commits for the same thing, what else can we do?
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:[~2015-03-27 2:16 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
2014-10-16 19:42 ` Michael Opdenacker
2015-03-27 1:55 ` Michael Opdenacker
2015-03-27 2:16 ` Michael Opdenacker [this message]
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=5514BD68.4000605@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