From: Ingo Molnar <mingo@elte.hu>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-kernel@vger.kernel.org, trivial@kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>,
jason.wessel@windriver.com
Subject: Re: [PATCH 2/4] perf: fix common misspellings
Date: Tue, 22 Mar 2011 12:44:05 +0100 [thread overview]
Message-ID: <20110322114405.GE4448@elte.hu> (raw)
In-Reply-To: <AANLkTik7wKdf_yCukg7RAAE5PWXw5YkAG=hSBuSn1wn9@mail.gmail.com>
* Lucas De Marchi <lucas.de.marchi@gmail.com> wrote:
> Hi Ingo,
>
> [ CC'ing Randy Dunlap and Jason Wessel ]
>
> On Tue, Mar 22, 2011 at 07:37, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Lucas De Marchi <lucas.de.marchi@gmail.com> wrote:
> >
> >> They were generated by 'codespell' and then manually reviewed.
> >>
> >> Signed-off-by: Lucas De Marchi <lucas.demarchi@profusion.mobi>
> >> ---
> >> arch/mips/kernel/perf_event_mipsxx.c | 2 +-
> >> arch/powerpc/kernel/perf_event.c | 2 +-
> >> arch/sparc/kernel/perf_event.c | 2 +-
> >> arch/x86/kernel/cpu/perf_event.c | 2 +-
> >> arch/x86/kernel/cpu/perf_event_p4.c | 8 ++++----
> >> include/linux/perf_event.h | 2 +-
> >> tools/perf/util/string.c | 2 +-
> >> 7 files changed, 10 insertions(+), 10 deletions(-)
> >
> > Hm, half of these do not apply anymore.
> >
> > Since they are auto-generated, mind sending one large spelling fixes patch to
> > Linus (for the whole kernel), at the end of the merge window, instead of these
> > zillions of small commits which just clutter the patchflow? That makes it a
> > heck of a lot easier to verify and handle for everyone involved.
>
> I agree with you, but last time I tried a large patch for fixing this
> I've been told to split the patches for each maintainer
> (http://kerneltrap.org/mailarchive/linux-kernel/2010/9/7/4616618). As
> you noticed it's a pain to apply them and it's even more for splitting
> in a per maintainer basis since it touches a lot of files.
>
> Randy, Jason: as you see maybe the split approach was not a good one.
>
> I'am all for applying this once, as Ingo said.
Well, ultimately it's up to Linus (i've Cc:-ed him).
For such pure spelling fixes i think what matters most is the timing, so that
it impacts outstanding trees in the smallest possible way. For that the best
timing would right before -rc1 - i.e. this week - as that is the moment when
the outstanding queues are the shortest.
Could you send the diffstat of the big, combined patch - how large is it total?
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-22 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 13:40 [PATCH 1/4] lockdep: fix common misspellings Lucas De Marchi
2011-03-18 13:40 ` [PATCH 2/4] perf: " Lucas De Marchi
2011-03-22 10:37 ` Ingo Molnar
2011-03-22 11:27 ` Lucas De Marchi
2011-03-22 11:44 ` Ingo Molnar [this message]
2011-03-22 12:07 ` Lucas De Marchi
2011-03-22 12:33 ` Ingo Molnar
2011-03-22 12:39 ` Lucas De Marchi
2011-03-22 16:31 ` Linus Torvalds
2011-03-22 16:48 ` Lucas De Marchi
2011-03-18 13:40 ` [PATCH 3/4] sched: " Lucas De Marchi
2011-03-18 13:40 ` [PATCH 4/4] tracing: Fix " Lucas De Marchi
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=20110322114405.GE4448@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@profusion.mobi \
--cc=randy.dunlap@oracle.com \
--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