From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2 1/2] ARM: vexpress: addition of MPS2 platform support for v4.7
Date: Tue, 26 Apr 2016 11:31:49 +0100 [thread overview]
Message-ID: <571F4395.80809@arm.com> (raw)
In-Reply-To: <6374181.eVf0heegjj@wuerfel>
On 26/04/16 11:26, Arnd Bergmann wrote:
> On Tuesday 26 April 2016 11:18:22 Sudeep Holla wrote:
>>
>> Thanks for having a look at this.
>>
>>> However, the way we pull them in, I need them separately for dts, defconfig and
>>> the rest. This means only one or two patches for each branch, which is getting
>>> slightly silly at that point, so you could just send them as patches,
>>> or I can cherry-pick the changes into the individual branches to save you
>>> yet another respin.
>>
>> Sure, I have pushed 3 branches accordingly:
>> 1. for-next/mps2
>> 2. for-next/mps2-dt
>> 3. for-next/mps2-defconfig
>>
>> @ git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
>>
>> Let me know if that's fine for you. I can tag and send PR if needed.
>
> The split is fine, and as I said before, I could also just cherry-pick
> the individual patches from it, but if you want me to pull the branches
> please add the signed tags.
>
I am fine if you can cherry-pick the patches.
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-04-26 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 16:31 [GIT PULL v2 1/2] ARM: vexpress: addition of MPS2 platform support for v4.7 Sudeep Holla
2016-04-25 16:31 ` [GIT PULL v2 2/2] ARM: vexpress: Updates " Sudeep Holla
2016-04-25 21:03 ` Arnd Bergmann
2016-04-25 21:06 ` [GIT PULL v2 1/2] ARM: vexpress: addition of MPS2 platform support " Arnd Bergmann
2016-04-26 10:18 ` Sudeep Holla
2016-04-26 10:26 ` Arnd Bergmann
2016-04-26 10:31 ` Sudeep Holla [this message]
2016-04-26 10:53 ` Arnd Bergmann
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=571F4395.80809@arm.com \
--to=sudeep.holla@arm.com \
--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