From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] [for arm-soc] mach-tango updates for v4.8
Date: Tue, 5 Jul 2016 14:32:31 +0200 [thread overview]
Message-ID: <577BA8DF.9080603@free.fr> (raw)
In-Reply-To: <57726597.8030501@sigmadesigns.com>
On 28/06/2016 13:55, Marc Gonzalez wrote:
> Hello arm-soc maintainers,
>
> Could you please merge the following patches?
>
> Marc Gonzalez (2):
> ARM: tango: add HOTPLUG_CPU support
> Update ARM/TANGO section
Hello Olof,
I see you've just merged a large number of patches in the for-next branch.
https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git/log/?h=for-next
I think you overlooked the two patches in this thread:
[PATCH v4 1/2] ARM: tango: add HOTPLUG_CPU support
[PATCH v3 2/2] Update ARM/TANGO section
Could you merge these patches as well?
Regards.
next prev parent reply other threads:[~2016-07-05 12:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:55 [PATCH v3 0/2] [for arm-soc] mach-tango updates for v4.8 Marc Gonzalez
2016-06-28 11:59 ` [PATCH v3 1/2] ARM: tango: add HOTPLUG_CPU support Marc Gonzalez
2016-06-28 11:59 ` Marc Gonzalez
2016-06-28 12:30 ` Robin Murphy
2016-06-28 12:30 ` Robin Murphy
2016-06-28 15:04 ` Marc Gonzalez
2016-06-28 15:04 ` Marc Gonzalez
2016-06-28 15:16 ` Robin Murphy
2016-06-28 15:16 ` Robin Murphy
2016-06-29 12:28 ` Marc Gonzalez
2016-06-29 12:28 ` Marc Gonzalez
2016-06-29 12:21 ` [PATCH v4 " Marc Gonzalez
2016-06-29 12:21 ` Marc Gonzalez
2016-06-28 12:01 ` [PATCH v3 2/2] Update ARM/TANGO section Marc Gonzalez
2016-07-05 12:32 ` Mason [this message]
2016-07-06 3:57 ` [PATCH v3 0/2] [for arm-soc] mach-tango updates for v4.8 Olof Johansson
2016-07-06 20:04 ` Arnd Bergmann
2016-07-07 4:45 ` Olof Johansson
2016-07-07 8:50 ` Mason
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=577BA8DF.9080603@free.fr \
--to=slash.tmp@free.fr \
--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 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.