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;
MIME-Version: 1.0
References: <20230702195057.1787686-1-sashal@kernel.org>
In-Reply-To: <20230702195057.1787686-1-sashal@kernel.org>
From:   Brian Norris <briannorris@chromium.org>
Date:   Mon, 10 Jul 2023 15:46:21 -0700
Message-ID: <CA+ASDXMZ_ZnJfpsY-8ZRByiox8HCSZeY08MvGSpznLYBtVR1bw@mail.gmail.com>
Subject: Re: [PATCH AUTOSEL 6.4 01/12] platform/chrome: cros_ec: Report EC
 panic as uevent
To:     Sasha Levin <sashal@kernel.org>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        Rob Barnes <robbarnes@google.com>,
        Prashant Malani <pmalani@chromium.org>,
        Tzung-Bi Shih <tzungbi@kernel.org>, bleung@chromium.org,
        chrome-platform@lists.linux.dev
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sun, Jul 2, 2023 at 12:51=E2=80=AFPM Sasha Levin <sashal@kernel.org> wro=
te:
>
> From: Rob Barnes <robbarnes@google.com>
>
> [ Upstream commit 2cbf475a04b2ae3d722bbe41742e5d874a027fc3 ]
>
> Create a uevent when an EC panic is detected. This will allow udev rules
> to trigger when a panic occurs. For example, a udev rule could be added t=
o
> capture an EC coredump. This approach avoids the need to stuff all the
> processing into the driver.
>
> Signed-off-by: Rob Barnes <robbarnes@google.com>
> Reviewed-by: Prashant Malani <pmalani@chromium.org>
> Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
> Link: https://lore.kernel.org/r/20230509232624.3120347-1-robbarnes@google=
.com
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  drivers/platform/chrome/cros_ec_lpc.c | 3 +++
>  1 file changed, 3 insertions(+)

What sorcery determined this was a valid for-linux-stable patch? It's
a new feature, and definitely not a for-stable candidate. Please
remove this from the queue.

Brian