From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: let the doc follow core code move
Date: Thu, 14 Jun 2012 14:58:04 +0100 [thread overview]
Message-ID: <4FD9EDEC.9020707@cam.ac.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1206141544080.8644@pobox.suse.cz>
On 6/14/2012 2:45 PM, Jiri Kosina wrote:
> On Thu, 14 Jun 2012, Jonathan Cameron wrote:
>
>>> As the IIO core code has been moved out of staging, let the appropriate
>>> documentation appear in Documentation/iio (which is what
>>> drivers/iio/Kconfig suggests as a location to look for it anyway).
>>>
>> I'd really rather not do this just yet. There are elements that are out
>> of date or downright wrong in here. Much like the drivers, these should
>> get some careful review before they go anywhere.
>>
>> For now we have carefully only moved abi docs that have been
>> carefully sanity checked first (and even then a few 'interesting'
>> corners made it through).
>>
>> Obviously we'd like to do that pretty soon!
>> In the meantime it comes down to that old story of wrong docs
>> perhaps being worse than no docs.
>
> Oh well, I see.
>
> So at least we need the patch below.
Fair enough I suppose.
>
>
>
>
> From: Jiri Kosina<jkosina@suse.cz>
> Subject: [PATCH] iio: drop wrong reference from Kconfig
>
> The documentation lives in drivers/staging/iio/Documentation, but
> according to Jonathan it's obsolete and needs fixing.
>
> Signed-off-by: Jiri Kosina<jkosina@suse.cz>
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/iio/Kconfig | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
> index 56eecef..2ec93da 100644
> --- a/drivers/iio/Kconfig
> +++ b/drivers/iio/Kconfig
> @@ -8,8 +8,7 @@ menuconfig IIO
> help
> The industrial I/O subsystem provides a unified framework for
> drivers for many different types of embedded sensors using a
> - number of different physical interfaces (i2c, spi, etc). See
> - Documentation/iio for more information.
> + number of different physical interfaces (i2c, spi, etc).
>
> if IIO
>
>
prev parent reply other threads:[~2012-06-14 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:28 [PATCH] iio: let the doc follow core code move Jiri Kosina
2012-06-14 13:37 ` Jonathan Cameron
2012-06-14 13:45 ` Jiri Kosina
2012-06-14 13:58 ` 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=4FD9EDEC.9020707@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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.