From: Ezequiel Garcia <ezequiel@collabora.com>
To: Hans Verkuil <hans.verkuil@cisco.com>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
Helen Koike <helen.koike@collabora.com>,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH 0/2] Some cleanups for ancillary drivers autoselect
Date: Mon, 15 Jul 2019 18:23:14 -0300 [thread overview]
Message-ID: <20190715212316.352-1-ezequiel@collabora.com> (raw)
Hi Mauro, Hans:
While developing the Rockchip ISP1 driver Helen and I noticed
that the MEDIA_SUBDRV_AUTOSELECT option was a bit confusing,
hiding some menu options, preventing us from jumping to sensor
drivers via the numbered menuconfig shortcuts.
Then, I noticed a user on IRC falling on the same trap,
and so decided the problem was common enough it was worth
a try.
Thanks!
Eze
Ezequiel Garcia (2):
media: Don't default-enable "ancillary driver autoselect" if EMBEDDED
media: Don't hide any menu if "ancillary drivers autoselect" is
enabled
drivers/media/Kconfig | 2 +-
drivers/media/dvb-frontends/Kconfig | 1 -
drivers/media/i2c/Kconfig | 1 -
drivers/media/spi/Kconfig | 1 -
drivers/media/tuners/Kconfig | 1 -
5 files changed, 1 insertion(+), 5 deletions(-)
--
2.22.0
next reply other threads:[~2019-07-15 21:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 21:23 Ezequiel Garcia [this message]
2019-07-15 21:23 ` [PATCH 1/2] media: Don't default-enable "ancillary driver autoselect" if EMBEDDED Ezequiel Garcia
2019-07-15 21:23 ` [PATCH 2/2] media: Don't hide any menu if "ancillary drivers autoselect" is enabled Ezequiel Garcia
2019-07-25 15:57 ` Mauro Carvalho Chehab
2019-07-25 16:01 ` Hans Verkuil
2019-07-25 17:05 ` Ezequiel Garcia
2019-07-25 17:29 ` Chen-Yu Tsai
2019-07-25 18:41 ` Mauro Carvalho Chehab
2019-07-25 19:00 ` Helen Koike
2019-07-25 19:16 ` Mauro Carvalho Chehab
2019-07-25 23:55 ` Ezequiel Garcia
2019-07-26 2:09 ` Mauro Carvalho Chehab
2019-07-26 2:54 ` Ezequiel Garcia
2019-07-27 0:17 ` Ezequiel Garcia
2019-07-27 1:39 ` Mauro Carvalho Chehab
2019-07-25 17:45 ` Mauro Carvalho Chehab
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=20190715212316.352-1-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
/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.