public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: MSM PMU Support in Commit ee3c454b
Date: Fri, 07 May 2010 11:59:27 -0700	[thread overview]
Message-ID: <1273258767.3542.80.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100507182637.GE7887@n2100.arm.linux.org.uk>

On Fri, 2010-05-07 at 19:26 +0100, Russell King - ARM Linux wrote:
> On Fri, May 07, 2010 at 11:24:07AM -0700, Daniel Walker wrote:
> > On Fri, 2010-05-07 at 19:15 +0100, Russell King - ARM Linux wrote:
> > > Maybe I'll just keep the devel-stable branch entirely separate until
> > > the devel stuff has been merged, and then MSM can be sorted at some
> > > point later.  This unfortunately means that devel-stable drops out of
> > > linux-next.  It also means that linux-next is at risk of missing the
> > > merge window... again.
> > 
> > Would it matter if you just did a revert on the MSM pmu patch ?
> 
> No - and it might be better if you did it.  I could do it on my
> devel-stable branch but then that'll cause you problems if you
> apply a patch from Will for this (but I think you'll have problems
> with that whichever way.)

I'll add a revert on my for-russell branch, then you can pull that. Is
that what your thinking ?

Daniel

  reply	other threads:[~2010-05-07 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 17:02 MSM PMU Support in Commit ee3c454b Will Deacon
2010-05-07 17:12 ` Daniel Walker
2010-05-07 18:03   ` Russell King - ARM Linux
2010-05-07 18:04   ` Will Deacon
2010-05-07 18:16     ` Russell King - ARM Linux
2010-05-07 18:15 ` Russell King - ARM Linux
2010-05-07 18:24   ` Daniel Walker
2010-05-07 18:26     ` Russell King - ARM Linux
2010-05-07 18:59       ` Daniel Walker [this message]
2010-05-07 19:01         ` Russell King - ARM Linux
2010-05-07 19:20           ` Daniel Walker
2010-05-09  9:33   ` Will Deacon

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=1273258767.3542.80.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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