From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 0/8] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer
Date: Thu, 11 Aug 2016 11:58:48 +0100 [thread overview]
Message-ID: <20160811105848.GA25680@red-moon> (raw)
In-Reply-To: <CADyBb7tZDT2LMGnsWW_orR37dsfseijLEjzn59rLW9tbbxKVPQ@mail.gmail.com>
On Thu, Aug 11, 2016 at 06:22:03PM +0800, Fu Wei wrote:
> Hi Hanjun, Tomasz,
>
> On 11 August 2016 at 18:15, Hanjun Guo <hanjun.guo@linaro.org> wrote:
> > Hi,
> >
> > On 2016/8/11 17:37, Tomasz Nowicki wrote:
> >>
> >> Hi Fu,
> >>
> >> Do you mind if I send IORT series where new drivers/acpi/arm64 directory
> >> would be introduced in first place ? This means your GTDT set would
> >> depend on IORT.
> >
> >
> > I think it's reasonable as the IORT for ITS is the key device enablement
> > for PCI MSI. I talked to Fuwei offline and he is fine with it.
>
> That's no problem at all, will do.
>
> Can I do this:
> (1)apply Tomasz's v8 patchset on the master branch of upstream kernel
> (2)rebase my v10 on the top of Tomasz's v8
> (3)git format-patch as v11, repost it
>
> Is that OK for everyone? :-)
I do not think you need a v11 just to remove the drivers/acpi/arm64
directory creation, you need to get Daniel/Thomas review/ack on
the respective patches though, I do not see the point of churning
out another series just because drivers/acpi/arm64 is now created
in the IORT patch series. If v10 is ok you will rebase it on top of
Tomasz's series and mention the dependency in the respective pull
request.
If there is need for a v11 following Daniel/Thomas review yes,
you can proceed as above.
Lorenzo
next prev parent reply other threads:[~2016-08-11 10:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 12:19 [PATCH v10 0/8] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 1/8] clocksource/drivers/arm_arch_timer: Move enums and defines to header file fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 2/8] clocksource/drivers/arm_arch_timer: Add a new enum for spi type fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 3/8] clocksource/drivers/arm_arch_timer: Improve printk relevant code fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 4/8] acpi/arm64: Add GTDT table parse driver fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 5/8] clocksource/drivers/arm_arch_timer: Simplify ACPI support code fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 6/8] acpi/arm64: Add memory-mapped timer support in GTDT driver fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 7/8] clocksource/drivers/arm_arch_timer: Add GTDT support for memory-mapped timer fu.wei at linaro.org
2016-07-26 12:19 ` [PATCH v10 8/8] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver fu.wei at linaro.org
2016-08-11 9:37 ` [PATCH v10 0/8] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer Tomasz Nowicki
2016-08-11 10:15 ` Hanjun Guo
2016-08-11 10:22 ` Fu Wei
2016-08-11 10:58 ` Lorenzo Pieralisi [this message]
2016-08-17 19:01 ` Timur Tabi
2016-08-18 7:48 ` 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=20160811105848.GA25680@red-moon \
--to=lorenzo.pieralisi@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;
as well as URLs for NNTP newsgroup(s).