From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: David Brown <davidb@codeaurora.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Mundt <lethal@linux-sh.org>,
x86@kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] cpuidle: Consistent spelling of cpuidle_idle_call()
Date: Fri, 5 Aug 2011 08:47:57 +0900 [thread overview]
Message-ID: <20110804234755.GA13321@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E3AD5E7.6040105@codeaurora.org>
On Thu, Aug 04, 2011 at 10:24:55AM -0700, Stephen Boyd wrote:
> On 08/04/2011 09:24 AM, David Brown wrote:
> > Commit a0bfa1373859e9d11dc92561a8667588803e42d8 mispells
> > cpuidle_idle_call() on ARM and SH code. Fix this to be consistent.
> > The referenced commit breaks compilation on ARM, and appears it would
> > do so on SH as well.
> Mark Brown sent this patch[1] months ago when this build breakage was
> noticed in linux-next. What happened to that patch? It looks like the
> patch that introduced the breakage was pulled from linux-next shortly
> after and then reintroduced today.
Yeah, as far as I remember Stephen applied my patch to -next as Len
didn't respond to it.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] cpuidle: Consistent spelling of cpuidle_idle_call()
Date: Thu, 04 Aug 2011 23:47:57 +0000 [thread overview]
Message-ID: <20110804234755.GA13321@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E3AD5E7.6040105@codeaurora.org>
On Thu, Aug 04, 2011 at 10:24:55AM -0700, Stephen Boyd wrote:
> On 08/04/2011 09:24 AM, David Brown wrote:
> > Commit a0bfa1373859e9d11dc92561a8667588803e42d8 mispells
> > cpuidle_idle_call() on ARM and SH code. Fix this to be consistent.
> > The referenced commit breaks compilation on ARM, and appears it would
> > do so on SH as well.
> Mark Brown sent this patch[1] months ago when this build breakage was
> noticed in linux-next. What happened to that patch? It looks like the
> patch that introduced the breakage was pulled from linux-next shortly
> after and then reintroduced today.
Yeah, as far as I remember Stephen applied my patch to -next as Len
didn't respond to it.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpuidle: Consistent spelling of cpuidle_idle_call()
Date: Fri, 5 Aug 2011 08:47:57 +0900 [thread overview]
Message-ID: <20110804234755.GA13321@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E3AD5E7.6040105@codeaurora.org>
On Thu, Aug 04, 2011 at 10:24:55AM -0700, Stephen Boyd wrote:
> On 08/04/2011 09:24 AM, David Brown wrote:
> > Commit a0bfa1373859e9d11dc92561a8667588803e42d8 mispells
> > cpuidle_idle_call() on ARM and SH code. Fix this to be consistent.
> > The referenced commit breaks compilation on ARM, and appears it would
> > do so on SH as well.
> Mark Brown sent this patch[1] months ago when this build breakage was
> noticed in linux-next. What happened to that patch? It looks like the
> patch that introduced the breakage was pulled from linux-next shortly
> after and then reintroduced today.
Yeah, as far as I remember Stephen applied my patch to -next as Len
didn't respond to it.
next prev parent reply other threads:[~2011-08-04 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 16:24 [PATCH] cpuidle: Consistent spelling of cpuidle_idle_call() David Brown
2011-08-04 16:24 ` David Brown
2011-08-04 16:24 ` David Brown
2011-08-04 17:24 ` Stephen Boyd
2011-08-04 17:24 ` Stephen Boyd
2011-08-04 17:24 ` Stephen Boyd
2011-08-04 23:47 ` Mark Brown [this message]
2011-08-04 23:47 ` Mark Brown
2011-08-04 23:47 ` Mark Brown
2011-08-05 10:57 ` Sergei Shtylyov
2011-08-05 10:57 ` Sergei Shtylyov
2011-08-05 10:57 ` Sergei Shtylyov
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=20110804234755.GA13321@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=davidb@codeaurora.org \
--cc=khilman@deeprootsystems.com \
--cc=len.brown@intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sboyd@codeaurora.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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.