From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Michael Wang <wangyun@linux.vnet.ibm.com>,
mingo@redhat.com, linaro-kernel@lists.linaro.org,
patches@linaro.org, linux-kernel@vger.kernel.org,
robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com,
arvind.chauhan@arm.com
Subject: Re: [PATCH 1/2] sched: Optimize build_sched_domains() for saving first SD node for a cpu
Date: Wed, 5 Jun 2013 15:03:58 +0200 [thread overview]
Message-ID: <20130605130358.GL27176@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKohpomJOGKoX9+HWkiGshUwTG9yKbn=M25xJvEYVZGnmj9Bkg@mail.gmail.com>
On Wed, Jun 05, 2013 at 06:12:15PM +0530, Viresh Kumar wrote:
> On 5 June 2013 16:34, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, Jun 05, 2013 at 10:37:29AM +0530, Viresh Kumar wrote:
>
> >> See if below one looks better (Attached too in case gmail screws up
> >> my mail)..
>
> > Applying patch
> > patches/viresh_kumar-_patch__sched-optimize_build_sched_domains_for_saving_first_sd.patch
> > patching file kernel/sched/core.c
> > patch: **** malformed patch at line 56: cpumask *cpu_map,
>
> You tried to apply patch from mail or attachment? I requested to
> pick attachment as gmail's copy-paste screws up patches.
>
>From email; that's what my mailer is scripted for. TBH I didn't even
notice the attachment.
I'll go prod at the attachment.
prev parent reply other threads:[~2013-06-05 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 11:20 [PATCH 1/2] sched: Optimize build_sched_domains() for saving first SD node for a cpu Viresh Kumar
2013-06-04 11:20 ` [PATCH 2/2] sched: Remove unused params of build_sched_domain() Viresh Kumar
2013-06-05 4:42 ` [PATCH 1/2] sched: Optimize build_sched_domains() for saving first SD node for a cpu Michael Wang
2013-06-05 5:07 ` Viresh Kumar
2013-06-05 5:26 ` Michael Wang
2013-06-05 11:04 ` Peter Zijlstra
2013-06-05 12:42 ` Viresh Kumar
2013-06-05 13:03 ` Peter Zijlstra [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=20130605130358.GL27176@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@linaro.org \
--cc=wangyun@linux.vnet.ibm.com \
/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