From: Michael Ellerman <michael@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Subject: Re: [PATCH V3 2/2] powerpc, perf: BHRB filter configuration should follow the task
Date: Tue, 23 Jul 2013 23:20:51 +1000 [thread overview]
Message-ID: <20130723132050.GA31944@concordia> (raw)
In-Reply-To: <1374475696.3916.35.camel@pasglop>
On Mon, Jul 22, 2013 at 04:48:16PM +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2013-07-22 at 12:09 +0530, Anshuman Khandual wrote:
> > These patches have not been applied yet. Would like me to correct
> > these spellings myself and send out again. Please do let me know.
> > Thanks !
>
> No, it's ok, I'll add them to my batch.
>
> Usually I assume that perf related stuff goes through acme's perf tree
> so I might have overlooked them because of that.
>
> Michael, you're ok with these ?
Which Michael? :)
I haven't had time to really get my head around the BHRB code, so I
can't really say.
cheers
next prev parent reply other threads:[~2013-07-23 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 5:53 [PATCH V3 0/2] Improvement and fixes for BHRB Anshuman Khandual
2013-06-10 5:53 ` [PATCH V3 1/2] powerpc, perf: Ignore separate BHRB privilege state filter request Anshuman Khandual
2013-06-24 7:19 ` Michael Neuling
2013-06-10 5:53 ` [PATCH V3 2/2] powerpc, perf: BHRB filter configuration should follow the task Anshuman Khandual
2013-06-24 7:20 ` Michael Neuling
2013-07-22 6:39 ` Anshuman Khandual
2013-07-22 6:48 ` Benjamin Herrenschmidt
2013-07-23 13:20 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-10 5:25 [PATCH V3 0/2] Improvement and fixes for BHRB Anshuman Khandual
2013-06-10 5:25 ` [PATCH V3 2/2] powerpc, perf: BHRB filter configuration should follow the task Anshuman Khandual
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=20130723132050.GA31944@concordia \
--to=michael@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).