From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Tao Ren <taoren@fb.com>, Linus Walleij <linus.walleij@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Yu Lei <mine260309@gmail.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix invalid interrupt register access
Date: Wed, 3 Oct 2018 14:28:09 +0200 [thread overview]
Message-ID: <6e7703e4-461b-77bf-5c9d-cc9e91c5ef3d@linaro.org> (raw)
In-Reply-To: <966C48A9-98F7-4B2B-BCD0-FAF3066C5794@fb.com>
On 03/10/2018 09:46, Tao Ren wrote:
> On 10/2/18, 11:57 PM, "Linus Walleij" <linus.walleij@linaro.org>
> wrote:
>
>> My thought is go for (2) and do all changes in one patch :)
>
> No problem, Linus. One more question: looks like my first patch
> 4451d3f59f2a (fix set_next_event handler) is not merged back to
> "timers/core". Should I generate this patch on top of the first patch
> or on top of the current "timers/core"? Which one would be easier for
> you (or Daniel/Thomas)? Sorry I'm pretty new to the community..
Hi Tao,
the branch tip:timers/urgent will be merged in tip:/timers/core, so the
fixes will be propagated to the master branch.
Base your change in top of tip:timers/urgent, the merge will happen soon
and both fixes will end up in tip:timers/core.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-10-03 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 4:14 [PATCH] clocksource/drivers/fttmr010: fix invalid interrupt register access Tao Ren
2018-10-02 7:35 ` Linus Walleij
2018-10-02 7:35 ` Linus Walleij
2018-10-02 22:08 ` Tao Ren
2018-10-03 6:56 ` Linus Walleij
2018-10-03 6:56 ` Linus Walleij
2018-10-03 7:46 ` Tao Ren
2018-10-03 12:28 ` Daniel Lezcano [this message]
2018-10-03 21:05 ` Tao Ren
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=6e7703e4-461b-77bf-5c9d-cc9e91c5ef3d@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mine260309@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.