From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: <skomatineni@nvidia.com>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <hverkuil@xs4all.nl>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>
Subject: [PATCH v1 2/2] media: tegra-video: Allow building driver with COMPILE_TEST
Date: Tue, 29 Sep 2020 20:02:38 -0700 [thread overview]
Message-ID: <1601434958-29305-3-git-send-email-skomatineni@nvidia.com> (raw)
In-Reply-To: <1601434958-29305-1-git-send-email-skomatineni@nvidia.com>
This patch adds COMPILE_TEST option to Kconfig to allow building
it with COMPILE_TEST option.
Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
---
drivers/staging/media/tegra-video/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/tegra-video/Kconfig b/drivers/staging/media/tegra-video/Kconfig
index 1f35da4..3e03ddd 100644
--- a/drivers/staging/media/tegra-video/Kconfig
+++ b/drivers/staging/media/tegra-video/Kconfig
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0-only
config VIDEO_TEGRA
tristate "NVIDIA Tegra VI driver"
- depends on TEGRA_HOST1X
+ depends on TEGRA_HOST1X || COMPILE_TEST
depends on VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEOBUF2_DMA_CONTIG
--
2.7.4
next prev parent reply other threads:[~2020-09-30 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 3:02 [PATCH v1 0/2] Allow building Tegra video driver with COMPILE_TEST Sowjanya Komatineni
2020-09-30 3:02 ` [PATCH v1 1/2] gpu: host1x: Allow COMPILE_TEST to build host1x driver on all platforms Sowjanya Komatineni
2020-10-30 11:02 ` Hans Verkuil
2020-09-30 3:02 ` Sowjanya Komatineni [this message]
2020-09-30 17:34 ` [PATCH v1 2/2] media: tegra-video: Allow building driver with COMPILE_TEST Michał Mirosław
2020-09-30 17:59 ` Sowjanya Komatineni
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=1601434958-29305-3-git-send-email-skomatineni@nvidia.com \
--to=skomatineni@nvidia.com \
--cc=hverkuil@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).