linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] acpi, clocksource, kvm: add GTDT and ARM memory-mapped timer support
Date: Thu, 17 Mar 2016 10:07:30 -0500	[thread overview]
Message-ID: <56EAC832.6070203@codeaurora.org> (raw)
In-Reply-To: <1458199917-30699-1-git-send-email-fu.wei@linaro.org>

fu.wei at linaro.org wrote:
> From: Fu Wei <fu.wei@linaro.org>
>
> This patchset:
>      (1)Move some enums and marcos to header file for arm_arch_timer,
>      improve the pr_* code by defining "pr_fmt(fmt)" in arm_arch_timer.c
>
>      (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c
>      Parse all kinds of timer in GTDT table of ACPI:arch timer,
>      memory-mapped timer and SBSA Generic Watchdog timer.
>      This driver can help to simplify all the relevant timer drivers,
>      and separate all the ACPI GTDT knowledge from them.
>
>      (3)Simplify ACPI code for arch timer in arm_arch_timer.c
>
>      (4)Add memory-mapped timer support in arm_arch_timer.c

The SBSA watchdog driver is already in watchdog-next and will be merged 
into 4.6.  These five patches are necessary for the watchdog driver to 
probe on an ACPI system.

I'm guessing since that v4 was posted in the middle of the 4.6 merge 
window, that these patches won't make it and we'll have to wait until 
4.7 (at the earliest)?

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.

       reply	other threads:[~2016-03-17 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1458199917-30699-1-git-send-email-fu.wei@linaro.org>
2016-03-17 15:07 ` Timur Tabi [this message]
2016-03-18  0:41   ` [PATCH v4 0/5] acpi, clocksource, kvm: add GTDT and ARM memory-mapped timer support Rafael J. Wysocki
2016-03-18  0:55     ` Timur Tabi
2016-03-18  4:24       ` Fu Wei
2016-03-18  4:22     ` Fu Wei
2016-03-18  9:28       ` Fu Wei

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=56EAC832.6070203@codeaurora.org \
    --to=timur@codeaurora.org \
    --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).