From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Patryk Duda <pdk@semihalf.com>
Cc: Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@google.com>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
upstream@semihalf.com
Subject: Re: [PATCH v1] platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure
Date: Thu, 4 Aug 2022 09:00:43 +0000 [thread overview]
Message-ID: <YuuKu4b02siXj/TS@google.com> (raw)
In-Reply-To: <20220802154128.21175-1-pdk@semihalf.com>
On Tue, Aug 02, 2022 at 05:41:28PM +0200, Patryk Duda wrote:
> Fixes: 3300fdd630d4 ("platform/chrome: cros_ec: handle MKBP more events flag")
> Cc: <stable@vger.kernel.org> # 5.10+
Any concerns if removing the Cc tag? As I think a Fixes tag should be
sufficient. On a related note, why did you specify for only 5.10+?
> Signed-off-by: Patryk Duda <pdk@semihalf.com>
You should collect the Reviewed-by tags the patch already got as dropping
`ver_mask` initialization isn't a big change. I could do that for the patch
this time.
[...]
> v0 -> v1
> - Dropped `ver_mask` initialization.
Please start versioning from v1 next time.
next prev parent reply other threads:[~2022-08-04 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 16:09 [PATCH] platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure Patryk Duda
2022-07-14 16:31 ` Guenter Roeck
2022-07-18 3:20 ` Tzung-Bi Shih
2022-08-02 15:41 ` [PATCH v1] " Patryk Duda
2022-08-04 9:00 ` Tzung-Bi Shih [this message]
2022-08-04 10:59 ` Patryk Duda
2022-08-05 2:40 ` patchwork-bot+chrome-platform
2022-08-15 3:44 ` patchwork-bot+chrome-platform
2022-08-15 3:55 ` patchwork-bot+chrome-platform
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=YuuKu4b02siXj/TS@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=gwendal@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pdk@semihalf.com \
--cc=upstream@semihalf.com \
/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