linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Gwendal Grignou <gwendal@chromium.org>,
	groeck@chromium.org, rdunlap@infradead.org, bleung@chromium.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] platform: chrome: Simplify interrupt path
Date: Tue, 26 Jan 2021 10:25:35 +0100	[thread overview]
Message-ID: <161165311118.2160839.18188794339266196197.b4-ty@collabora.com> (raw)
In-Reply-To: <20210122054637.1422289-1-gwendal@chromium.org>

On Thu, 21 Jan 2021 21:46:35 -0800, Gwendal Grignou wrote:
> rrespective of the transport (i2c, spi, ish, rpmsg), have all cros ec
> interrupt stack call the threaded part (bottom half) of the interrupt
> handler.
> Fix an issue where EC could be stuck if it sends a message while the AP
> is not powered on.
> 
> Changes since v1:
> - fix merging issue and function comments syntax.
> 
> [...]

Applied, thanks!

[1/2] platform: cros_ec: Call interrupt bottom half in ISH or RPMSG mode
      commit: 24c69043be1725606e876b47d496a0f9f87d176a
[2/2] platform: cros_ec: Call interrupt bottom half at probe time
      commit: 4daeb395f1754340927d8d58269593e4e3b6afcd

Best regards,
-- 
Enric Balletbo i Serra <enric.balletbo@collabora.com>

      parent reply	other threads:[~2021-01-26 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  5:46 [PATCH v2 0/2] platform: chrome: Simplify interrupt path Gwendal Grignou
2021-01-22  5:46 ` [PATCH v2 1/2] platform: cros_ec: Call interrupt bottom half in ISH or RPMSG mode Gwendal Grignou
2021-01-22  5:46 ` [PATCH v2 2/2] platform: cros_ec: Call interrupt bottom half at probe time Gwendal Grignou
2021-01-26  9:25 ` Enric Balletbo i Serra [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=161165311118.2160839.18188794339266196197.b4-ty@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=bleung@chromium.org \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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).