From: Sudeep.KarkadaNagesha@arm•com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/6] ARM/ARM64 architected timer updates
Date: Wed, 14 Aug 2013 10:17:34 +0100 [thread overview]
Message-ID: <520B4B2E.1040700@arm.com> (raw)
In-Reply-To: <520B490A.4090109@linaro.org>
On 14/08/13 10:08, Daniel Lezcano wrote:
> On 08/13/2013 07:29 PM, Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm•com>
>>
>> This patch series adds support to configure the rate and enable the
>> event stream for architected timer. The event streams can be used to
>> impose a timeout on a WFE, to safeguard against any programming error
>> in case an expected event is not generated or even to implement
>> wfe-based timeouts for userspace locking implementations.
>>
>> Since the timer control register is reset to zero on warm boot, CPU
>> PM notifier is added to re-initialize it.
>
> It does not apply to my tree.
>
> Against which tree is this patchset ? Who is supposed to take it ?
>
As I had mentioned in previous version, because of the conflict, I had
to rebase it on 3.11-rc4
>> Changes v2->v3:
>> 1. Moved ARM and ARM64 changes into separate patches
>> 2. Added native hwcaps definations(ARM/ARM64) and compat-specific
>> definitions(ARM64) to the users for the event stream feature.
>
> Ok, we have the choice:
> 1. split the patchset into arch/arm changes and drivers/clocksource
> 2. I ack the patchset and Olof/Kevin take it
> 3. Olof/Kevin ack the patchset and I take it in my tree.
>
> This is really becoming fuzzy.
>
I am not sure if we need to split it. It would get too messy because of
dependencies. Once we have ACKs from all the corresponding maintainers,
it can go through one of the tree.
> If you want a maintainer to take a patchset you have to send an email
> --to him and --cc mailing list and others concerned by the patchset.
>
Ok understood.
Regards,
Sudeep
next prev parent reply other threads:[~2013-08-14 9:17 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 17:06 [PATCH 0/4] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-06-18 17:07 ` [PATCH 1/4] drivers: clocksource: configure event stream for ARM arch timer Sudeep KarkadaNagesha
2013-06-18 17:07 ` [PATCH 2/4] ARM: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-06-18 17:07 ` [PATCH 3/4] ARM/ARM64: arch_timer: remove __cpuinit attribute for arch_counter_set_user_access Sudeep KarkadaNagesha
2013-06-18 17:58 ` Sudeep KarkadaNagesha
2013-06-18 17:07 ` [PATCH 4/4] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-07-02 16:09 ` Jon Medhurst (Tixy)
2013-07-02 17:24 ` Sudeep KarkadaNagesha
2013-07-22 11:21 ` [PATCH v2 0/3] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-07-22 11:21 ` [PATCH v2 1/3] drivers: clocksource: configure event stream for ARM arch timer Sudeep KarkadaNagesha
2013-07-23 10:23 ` Catalin Marinas
2013-07-23 10:33 ` Will Deacon
2013-07-23 11:12 ` Catalin Marinas
2013-07-25 9:45 ` [PATCH v3 " Sudeep KarkadaNagesha
2013-08-12 13:32 ` Sudeep KarkadaNagesha
2013-07-22 11:21 ` [PATCH v2 2/3] ARM: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-07-22 11:21 ` [PATCH v2 3/3] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-08-02 9:32 ` [PATCH v2 0/3] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-08-02 9:48 ` Daniel Lezcano
2013-08-02 9:55 ` Sudeep KarkadaNagesha
2013-08-02 12:12 ` Daniel Lezcano
2013-08-05 16:25 ` Sudeep KarkadaNagesha
2013-08-06 8:09 ` Daniel Lezcano
2013-08-06 9:01 ` Sudeep KarkadaNagesha
2013-08-12 13:16 ` Daniel Lezcano
2013-08-13 17:29 ` [PATCH v3 0/6] " Sudeep KarkadaNagesha
2013-08-13 17:29 ` [PATCH v3 1/6] ARM/ARM64: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-08-14 8:50 ` Daniel Lezcano
2013-08-14 9:03 ` Marc Zyngier
2013-08-14 9:23 ` Daniel Lezcano
2013-08-13 17:29 ` [PATCH v3 2/6] drivers: clocksource: configure event stream for ARM arch timer Sudeep KarkadaNagesha
2013-08-13 17:29 ` [PATCH v3 3/6] ARM: arch_timer: configure and enable event stream Sudeep KarkadaNagesha
2013-08-13 17:29 ` [PATCH v3 4/6] ARM64: " Sudeep KarkadaNagesha
2013-08-20 13:27 ` Will Deacon
2013-08-20 14:27 ` Sudeep KarkadaNagesha
2013-08-20 16:16 ` Will Deacon
2013-08-20 16:23 ` Sudeep KarkadaNagesha
2013-08-20 17:08 ` Sudeep KarkadaNagesha
2013-08-21 17:52 ` Will Deacon
2013-08-13 17:29 ` [PATCH v3 5/6] drivers: clocksource: enable hwcaps for event stream on ARM arch timer Sudeep KarkadaNagesha
2013-08-13 17:29 ` [PATCH v3 6/6] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-08-14 9:08 ` [PATCH v3 0/6] ARM/ARM64 architected timer updates Daniel Lezcano
2013-08-14 9:17 ` Sudeep KarkadaNagesha [this message]
2013-08-14 10:51 ` Daniel Lezcano
2013-08-14 11:03 ` Sudeep KarkadaNagesha
2013-08-14 15:00 ` Daniel Lezcano
2013-08-20 17:14 ` Sudeep KarkadaNagesha
2013-08-23 9:26 ` Catalin Marinas
2013-08-23 9:57 ` Sudeep KarkadaNagesha
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=520B4B2E.1040700@arm.com \
--to=sudeep.karkadanagesha@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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