From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] v4l2-utils: ctl and compliance require libv4l2
Date: Tue, 28 Nov 2023 09:36:51 +0100 [thread overview]
Message-ID: <20231128083651.1044855-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231122161924.1478955-1-r.czerwinski@pengutronix.de>
Thanks, applied as e1af26862a3ef6c93e10caad9e45c6514a9d0e8b.
Michael
[sent from post-receive hook]
On Tue, 28 Nov 2023 09:36:50 +0100, Rouven Czerwinski <r.czerwinski@pengutronix.de> wrote:
> Both the v4l2-ctl and v4l2-compliance tool require that libv4l2 is
> available on the system since they are linked dynamically. Ensure that
> it is enabled when one of the tools is selected.
>
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> Message-Id: <20231122161924.1478955-1-r.czerwinski@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/v4l-utils.in b/rules/v4l-utils.in
> index d722aeb2531e..1394fbcd41c9 100644
> --- a/rules/v4l-utils.in
> +++ b/rules/v4l-utils.in
> @@ -73,6 +73,7 @@ config V4L_UTILS_RDSCTL
>
> config V4L_UTILS_V4L2COMPLIANCE
> bool
> + select V4L_UTILS_LIBV4L2
> prompt "install v4l2-compliance"
>
> config V4L_UTILS_V4L2DBG
> @@ -82,6 +83,7 @@ config V4L_UTILS_V4L2DBG
>
> config V4L_UTILS_V4L2CTL
> bool
> + select V4L_UTILS_LIBV4L2
> prompt "install v4l2-ctl"
>
> config V4L_UTILS_V4L2SYSFSPATH
prev parent reply other threads:[~2023-11-28 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:19 [ptxdist] [PATCH] " r.czerwinski
2023-11-28 8:36 ` Michael Olbrich [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=20231128083651.1044855-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=r.czerwinski@pengutronix.de \
/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