From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: David Frey <dpfrey@gmail.com>
Cc: linux-iio <linux-iio@vger.kernel.org>
Subject: Re: CONFIG_IIO_TRIGGERED_BUFFER lacks Kconfig description
Date: Mon, 8 Oct 2018 21:10:47 +0100 [thread overview]
Message-ID: <20181008211047.30c7986c@archlinux> (raw)
In-Reply-To: <d784af9b-c687-530d-4499-fed635a7409e@gmail.com>
On Wed, 3 Oct 2018 08:47:00 -0700
David Frey <dpfrey@gmail.com> wrote:
> Hi,
>
> I have noticed that CONFIG_IIO_TRIGGERED_BUFFER doesn't have any
> description in Kconfig. I'm not an expert on Kconfig, but I believe
> this means that it is not possible to set the config option explicitly
> using menuconfig. I see this as a problem because it means that you
> can't really build the necessary kernel config to support an out of tree
> driver which depends on CONFIG_IIO_TRIGGERED_BUFFER. If I'm wrong about
> this, please let me know why.
The basic answer is that it's a trade off between presenting more complex
options in menuconfig for in kernel drivers and supporting easy out of
tree builds. Is it particularly important for your usecase to have your
driver built out of tree and is not possible to patch the kernel to allow
it if you need to?
So basically provide a strong argument for why and lets see what others
think about this.
Jonathan
>
> Thanks,
> David
prev parent reply other threads:[~2018-10-09 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 15:47 CONFIG_IIO_TRIGGERED_BUFFER lacks Kconfig description David Frey
2018-10-08 20:10 ` Jonathan Cameron [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=20181008211047.30c7986c@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=dpfrey@gmail.com \
--cc=linux-iio@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 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).