From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ken Lin <kenlin5@quanta.corp-partner.google.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: "Benson Leung" <bleung@chromium.org>,
groeck@chromium.org, "Hans Verkuil" <hverkuil@xs4all.nl>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Tzung-Bi Shih" <tzungbi@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
chrome-platform@lists.linux.dev, linux-media@vger.kernel.org
Subject: Re: [PATCH] UPSTREAM: media: platform: cros-ec: Add Moxie to the match table
Date: Thu, 27 Mar 2025 08:23:01 +0100 [thread overview]
Message-ID: <5549a95e-938b-4560-9e60-146e5e0883c4@linaro.org> (raw)
In-Reply-To: <20250327103918.1.I704cb6f738208386a0d431d355169c6fdf0f51bc@changeid>
On 27/03/2025 03:39, Ken Lin wrote:
> The Google Moxie device uses the same approach as the Google Brask
> which enables the HDMI CEC via the cros-ec-cec driver.
>
> Hans Verkuil <hverkuil-cisco@xs4all.nl>,
> Mauro Carvalho Chehab <mchehab@kernel.org>,
> Reka Norman <rekanorman@chromium.org>,
> Stefan Adolfsson <sadolfsson@chromium.org>,
No clue what's that... and I don't get why you call it upstream. Follow
standard upstreaming processes and guides.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
If this is for your own projects, then obviously NAK.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-27 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 2:39 Ken Lin
2025-03-27 7:23 ` Krzysztof Kozlowski [this message]
2025-03-28 3:09 ` [PATCH] [v2] " Ken Lin
2025-03-28 7:55 ` Krzysztof Kozlowski
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=5549a95e-938b-4560-9e60-146e5e0883c4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=kenlin5@quanta.corp-partner.google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tzungbi@kernel.org \
--cc=u.kleine-koenig@baylibre.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
all inboxes | Powered by JetHome®