mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shirley Ma <mashirle@us.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	vivek@us.ibm.com, sri@us.ibm.com
Subject: Re: [RFC PATCH 0/1] sched: Add a new API to find the prefer idlest cpu
Date: Fri, 17 Aug 2012 09:58:11 -0700	[thread overview]
Message-ID: <1345222691.16533.7.camel@oc3660625478.ibm.com> (raw)
In-Reply-To: <1345222134.29668.63.camel@twins>

On Fri, 2012-08-17 at 18:48 +0200, Peter Zijlstra wrote:
> On Fri, 2012-08-17 at 08:39 -0700, Shirley Ma wrote:
> 
> > Hello Ingo, Peter,
> >         Have you had chance to review below patch?
> 
> Well no of course not, nobody CC'ed us..
> 
> Your patch submission sucks, you split the changelog and the actual
> patch into two different emails.
> 
> It doesn't mention who would be calling this and how often. Nor does
> it
> seem to explain where the cpumask arguments come from.
> 
> Please try again.

Thanks for your comments. I must be spoiled by net-dev maintainers. I
used to submit the patch this way thought my linux email in the past
many years. So I need to reply on the changelog for the actual patch? I
hope I won't make any more suck submissions again.

I will try to explain more details why this API needs to be exported.

Thanks again.
Shirley


      reply	other threads:[~2012-08-17 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  6:57 Shirley Ma
2012-07-23  6:59 ` [RFC PATCH 1/1] " Shirley Ma
2012-08-17 15:39 ` [RFC PATCH 0/1] " Shirley Ma
2012-08-17 16:48   ` Peter Zijlstra
2012-08-17 16:58     ` Shirley Ma [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=1345222691.16533.7.camel@oc3660625478.ibm.com \
    --to=mashirle@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sri@us.ibm.com \
    --cc=vivek@us.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
all inboxes | Powered by JetHome®