All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <david.ahern@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 3/3] sparc: perf: Make counting mode actually work
Date: Thu, 19 Mar 2015 18:34:44 +0000	[thread overview]
Message-ID: <550B16C4.2030703@oracle.com> (raw)
In-Reply-To: <1424747257-141252-3-git-send-email-david.ahern@oracle.com>

On 3/19/15 12:29 PM, David Miller wrote:
> From: David Ahern <david.ahern@oracle.com>
> Date: Thu, 19 Mar 2015 08:15:17 -0600
>
>> I realize M7 patches are on hold by you. This one (and the first one
>> in this set) has nothing to do with the M7. perf counting mode has
>> been broken for years on sparc; this patch fixes it.
>
> Not on hold, I'm simply waiting for them to be resubmitted.
>
> Anything not marked "under review" in patchwork needs to be explicitly
> resubmitting anew if you want me to consider it.
>
> Sorry if that wasn't clear.
>

Help me understand your process for patches ... I sent the patches to 
you and the mailing list. You responded only to the M7 patch (2 of 3). 
Should I take that to mean the entire set is invalidated? ie., how do I 
know if a patch is marked 'under review'?

If patches are not directly related to one another you want them as 
individual patches -- versus what I did here which is 3 individual 
patches that touch sparc/perf code.

Most of my patches have gone through acme and he gladly takes individual 
patches from a set.

  parent reply	other threads:[~2015-03-19 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  3:07 [PATCH 3/3] sparc: perf: Make counting mode actually work David Ahern
2015-03-19 14:15 ` David Ahern
2015-03-19 18:29 ` David Miller
2015-03-19 18:34 ` David Ahern [this message]
2015-03-19 18:44 ` David Miller
2015-03-19 18:47 ` David Ahern

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=550B16C4.2030703@oracle.com \
    --to=david.ahern@oracle.com \
    --cc=sparclinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.