All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: linux-kernel@vger.kernel.org, Prashant Malani <pmalani@chromium.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Guenter Roeck <groeck@chromium.org>,
	bleung@chromium.org
Subject: Re: [PATCH v2 1/2] platform/chrome: cros_ec_proto: Update feature check
Date: Wed, 18 Aug 2021 09:28:49 -0700	[thread overview]
Message-ID: <162930405787.1994945.17127194721609468006.b4-ty@chromium.org> (raw)
In-Reply-To: <20210803173619.91539-1-pmalani@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

On Tue, 3 Aug 2021 10:36:19 -0700, Prashant Malani wrote:
> EC feature flags now require more than 32 bits to be represented. In
> order to make cros_ec_check_features() usable for more recent features,
> update it to account for the extra 32 bits of features.

Applied the whole series, thanks!

[1/2] platform/chrome: cros_ec_proto: Update feature check
      commit: 3c645a03579d15de3b6ffd6d75801011d80416fc
[2/2] platform/chrome: cros_ec_typec: Use existing feature check
      commit: 7ddbb62d7b43e3334a52427cd9666d90a833bd19

Best regards,
-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2021-08-18 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 17:36 [PATCH v2 1/2] platform/chrome: cros_ec_proto: Update feature check Prashant Malani
2021-08-03 17:36 ` [PATCH v2 2/2] platform/chrome: cros_ec_typec: Use existing " Prashant Malani
2021-08-12 20:57 ` [PATCH v2 1/2] platform/chrome: cros_ec_proto: Update " Prashant Malani
2021-08-18 16:28 ` Benson Leung [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=162930405787.1994945.17127194721609468006.b4-ty@chromium.org \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmalani@chromium.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 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.