From: Krzysztof Kozlowski <krzk@kernel.org>
To: Julien Massot <julien.massot@collabora.com>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
benjamin.mugnier@foss.st.com, sylvain.petinot@foss.st.com
Cc: linux-media@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2] media: dt-bindings: st-vgxy61: relax data-lanes restriction
Date: Fri, 15 Mar 2024 12:36:12 +0100 [thread overview]
Message-ID: <63bb33ad-9687-4023-aa4e-253d83b5d458@kernel.org> (raw)
In-Reply-To: <20240315090345.1213957-1-julien.massot@collabora.com>
On 15/03/2024 10:03, Julien Massot wrote:
> The ST VGXY61 sensors support multiple lane numbers, as
> well as lane mapping.
> ---
> Changes in v2:
> Add minimum/maximum items to restrict lane index to 1..4.
> ---
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline), work on fork of kernel
(don't, instead use mainline) or you ignore some maintainers (really
don't). Just use b4 and everything should be fine, although remember
about `b4 prep --auto-to-cc` if you added new patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time, thus I will skip this patch entirely till you follow
the process allowing the patch to be tested.
Please kindly resend and include all necessary To/Cc entries.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-03-15 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 9:03 [PATCH v2] media: dt-bindings: st-vgxy61: relax data-lanes restriction Julien Massot
2024-03-15 9:22 ` Sakari Ailus
2024-03-29 8:32 ` Benjamin Mugnier
2024-03-15 11:36 ` Krzysztof Kozlowski [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=63bb33ad-9687-4023-aa4e-253d83b5d458@kernel.org \
--to=krzk@kernel.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=julien.massot@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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 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.