Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 4 Aug 2022 09:00:43 +0000
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
Message-ID: <YuuKu4b02siXj/TS@google.com>
References: <20220714160951.9364-1-pdk@semihalf.com>
 <20220802154128.21175-1-pdk@semihalf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220802154128.21175-1-pdk@semihalf.com>
Precedence: bulk

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.