From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] Add support for legacy SCPI protocol
Date: Wed, 19 Oct 2016 09:43:51 -0700 [thread overview]
Message-ID: <7hpomw8f20.fsf@baylibre.com> (raw)
In-Reply-To: <4aa21ebe-446e-6343-238c-515718cbb162@arm.com> (Sudeep Holla's message of "Wed, 19 Oct 2016 17:10:10 +0100")
Sudeep Holla <sudeep.holla@arm.com> writes:
> On 19/10/16 16:59, Kevin Hilman wrote:
[...]
>>
>> Sudeep, will this be an immutable branch? (or could you put a tag at an
>> immutable place on this branch?) I'd like to include this in my amlogic
>> integration branch for broader testing.
>>
>
> If you plan to test SCPI(which is enabled in defconfig), then you need
> all the patches in the branch[1]. I will tag once I get a build success
> from kbuild robot and I do some testing. In short, immutable tag = PR
> tag IMO. The only thing I can drop from the list is DT bindings patch.
>
> Let me know if you are fine using the same tag ? Or you can propose any
> other alternative, I am fine by that too.
I'm currently using your scpi-updates/for-next branch, so a tag at (or
near) there should be fine after you've validated it.
Thanks,
Kevin
prev parent reply other threads:[~2016-10-19 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 12:51 [PATCH v5 0/5] Add support for legacy SCPI protocol Neil Armstrong
2016-10-19 12:51 ` [PATCH v5 1/5] scpi: Add alternative legacy structures, functions and macros Neil Armstrong
2016-10-19 12:51 ` [PATCH v5 2/5] scpi: Do not fail if get_capabilities is not implemented Neil Armstrong
2016-10-19 12:51 ` [PATCH v5 3/5] scpi: Add support for Legacy match table for Amlogic GXBB SoC Neil Armstrong
2016-10-19 12:51 ` [PATCH v5 4/5] ARM64: dts: meson-gxbb: Add SRAM node Neil Armstrong
2016-10-19 12:51 ` [PATCH v5 5/5] ARM64: dts: meson-gxbb: Add SCPI with cpufreq & sensors Nodes Neil Armstrong
2016-10-19 14:44 ` [PATCH v5 0/5] Add support for legacy SCPI protocol Sudeep Holla
2016-10-19 15:56 ` Kevin Hilman
2016-10-19 15:59 ` Kevin Hilman
2016-10-19 16:10 ` Sudeep Holla
2016-10-19 16:43 ` Kevin Hilman [this message]
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=7hpomw8f20.fsf@baylibre.com \
--to=khilman@baylibre.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;
as well as URLs for NNTP newsgroup(s).