From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] v4l-utils: drop libv4l2 dependency for v4l2-compliance/ctl
Date: Mon, 31 May 2021 09:25:37 +0200 [thread overview]
Message-ID: <20210531072537.840422-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20210527083104.17953-1-m.felsch@pengutronix.de>
Thanks, applied as 59fd0963e99d6ae7652cb43793dce577dfecfc63.
Michael
[sent from post-receive hook]
On Mon, 31 May 2021 09:25:37 +0200, Marco Felsch <m.felsch@pengutronix.de> wrote:
> Since upstream commit bb28f870 ("v4l2-compliance/ctl: drop libv4l2
> dependency if NO_LIBV4L2 is defined") both tools can be build without
> libv4l2.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> Message-Id: <20210527083104.17953-1-m.felsch@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/v4l-utils.in b/rules/v4l-utils.in
> index b2254ea1ec07..de7cb374ba6f 100644
> --- a/rules/v4l-utils.in
> +++ b/rules/v4l-utils.in
> @@ -72,7 +72,6 @@ config V4L_UTILS_RDSCTL
>
> config V4L_UTILS_V4L2COMPLIANCE
> bool
> - select V4L_UTILS_LIBV4L2
> prompt "install v4l2-compliance"
>
> config V4L_UTILS_V4L2DBG
> @@ -82,7 +81,6 @@ config V4L_UTILS_V4L2DBG
>
> config V4L_UTILS_V4L2CTL
> bool
> - select V4L_UTILS_LIBV4L2
> prompt "install v4l2-ctl"
>
> config V4L_UTILS_V4L2SYSFSPATH
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-05-31 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 8:31 [ptxdist] [PATCH] " Marco Felsch
2021-05-31 7:25 ` 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=20210531072537.840422-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=ptxdist@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