From: Jon Hunter <jon-hunter@ti.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1 v2] ARM: only call smp_send_stop() on SMP
Date: Fri, 27 Jul 2012 12:15:04 -0500 [thread overview]
Message-ID: <5012CC98.60206@ti.com> (raw)
In-Reply-To: <CAAwP0s2jTPM_ErDOFKXoe95_Xd=xjkuTAsDbLctQ08_QVNkakQ@mail.gmail.com>
Hi Javier,
On 06/25/2012 05:31 AM, Javier Martinez Canillas wrote:
> On Mon, Jun 25, 2012 at 10:49 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Mon, Jun 25, 2012 at 08:51:37AM +0800, Shawn Guo wrote:
>>> It seems the same patch has been there for a while.
>>>
>>> http://thread.gmane.org/gmane.linux.kernel/1303115
>>
>> Bah, why doesn't stuff like this get resent if nothing has happened for
>> a while?
>
> Indeed. At least other people that face the same issue (like me) sends
> similar patches to remind you :-)
I checked with Russell but this one is not in his patch tracking system
[1] and so still not queued. Can you submit this? Would be great to get
this one in.
Cheers
Jon
[1] http://www.arm.linux.org.uk/developer/patches/
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1 v2] ARM: only call smp_send_stop() on SMP
Date: Fri, 27 Jul 2012 12:15:04 -0500 [thread overview]
Message-ID: <5012CC98.60206@ti.com> (raw)
In-Reply-To: <CAAwP0s2jTPM_ErDOFKXoe95_Xd=xjkuTAsDbLctQ08_QVNkakQ@mail.gmail.com>
Hi Javier,
On 06/25/2012 05:31 AM, Javier Martinez Canillas wrote:
> On Mon, Jun 25, 2012 at 10:49 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Mon, Jun 25, 2012 at 08:51:37AM +0800, Shawn Guo wrote:
>>> It seems the same patch has been there for a while.
>>>
>>> http://thread.gmane.org/gmane.linux.kernel/1303115
>>
>> Bah, why doesn't stuff like this get resent if nothing has happened for
>> a while?
>
> Indeed. At least other people that face the same issue (like me) sends
> similar patches to remind you :-)
I checked with Russell but this one is not in his patch tracking system
[1] and so still not queued. Can you submit this? Would be great to get
this one in.
Cheers
Jon
[1] http://www.arm.linux.org.uk/developer/patches/
next prev parent reply other threads:[~2012-07-27 17:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 10:28 [PATCH 1/1 v2] ARM: only call smp_send_stop() on SMP Javier Martinez Canillas
2012-06-24 10:28 ` Javier Martinez Canillas
2012-06-25 0:51 ` Shawn Guo
2012-06-25 0:51 ` Shawn Guo
2012-06-25 8:09 ` Javier Martinez Canillas
2012-06-25 8:09 ` Javier Martinez Canillas
2012-06-25 8:49 ` Russell King - ARM Linux
2012-06-25 8:49 ` Russell King - ARM Linux
2012-06-25 10:31 ` Javier Martinez Canillas
2012-06-25 10:31 ` Javier Martinez Canillas
2012-07-27 17:15 ` Jon Hunter [this message]
2012-07-27 17:15 ` Jon Hunter
2012-07-27 20:44 ` Will Deacon
2012-07-27 20:44 ` Will Deacon
2012-07-27 21:06 ` Russell King - ARM Linux
2012-07-27 21:06 ` Russell King - ARM Linux
2012-07-27 21:40 ` Will Deacon
2012-07-27 21:40 ` Will Deacon
2012-07-28 10:08 ` Russell King - ARM Linux
2012-07-28 10:08 ` Russell King - ARM Linux
2012-07-28 12:11 ` Will Deacon
2012-07-28 12:11 ` Will Deacon
2012-07-28 14:26 ` Javier Martinez Canillas
2012-07-28 14:26 ` Javier Martinez Canillas
2012-07-29 21:31 ` Russell King - ARM Linux
2012-07-29 21:31 ` Russell King - ARM Linux
2012-07-30 9:22 ` Javier Martinez Canillas
2012-07-30 9:22 ` Javier Martinez Canillas
2012-07-30 14:35 ` Russell King - ARM Linux
2012-07-30 14:35 ` Russell King - ARM Linux
2012-07-30 14:51 ` Javier Martinez Canillas
2012-07-30 14:51 ` Javier Martinez Canillas
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=5012CC98.60206@ti.com \
--to=jon-hunter@ti.com \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=martinez.javier@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=tony@atomide.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 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.