public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Tao Ren <taoren@fb.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2] clocksource/drivers/fttmr010: fix invalid interrupt register access
Date: Fri, 7 Dec 2018 21:22:15 +0000	[thread overview]
Message-ID: <B46CD44C-2A40-4074-BA89-E34ECF95CE36@fb.com> (raw)
In-Reply-To: <47d85e8e-bf01-11a7-9c02-6d934d911178@linaro.org>

On 12/6/18, 11:04 PM, "Daniel Lezcano" <daniel.lezcano@linaro.org> wrote:
>
> On 07/12/2018 02:13, Tao Ren wrote:
>> Not sure if I missed any emails from you, but looks like the patch is not included in your tree? Are we planning to include the patch in 4.21 merge window?
>
> Yes, I have it in the tree. I updated the next branch.

Got it. Thank you for the confirmation, Daniel.

Thanks,
Tao Ren


      reply	other threads:[~2018-12-07 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 21:53 [PATCH v2] clocksource/drivers/fttmr010: fix invalid interrupt register access Tao Ren
2018-10-07 21:03 ` Linus Walleij
2018-10-10  5:50   ` Tao Ren
2018-11-05 18:43   ` Tao Ren
2018-11-05 18:50     ` Daniel Lezcano
2018-11-05 19:00       ` Tao Ren
2018-12-07  1:13         ` Tao Ren
2018-12-07  7:04           ` Daniel Lezcano
2018-12-07 21:22             ` Tao Ren [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=B46CD44C-2A40-4074-BA89-E34ECF95CE36@fb.com \
    --to=taoren@fb.com \
    --cc=linux-aspeed@lists.ozlabs.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