From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 5/5] iio: add configuration option for debug support
Date: Tue, 16 Jul 2013 17:11:07 +0100 [thread overview]
Message-ID: <07271c08-5b24-4d86-8833-4ff2e15c8bed@email.android.com> (raw)
In-Reply-To: <51E53811.6040100@metafoo.de>
Lars-Peter Clausen <lars@metafoo.de> wrote:
>On 07/16/2013 02:01 PM, Otavio Salvador wrote:
>> On Tue, Jul 16, 2013 at 7:26 AM, Lars-Peter Clausen <lars@metafoo.de>
>wrote:
>>> On 07/16/2013 11:58 AM, Jonathan Cameron wrote:
>>>> On 07/15/2013 03:22 PM, Otavio Salvador wrote:
>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>> seems a sensible facility to have available.
>>>>
>>>> Applied to the togreg branch of iio.git
>>>
>>> Can you update the Kconfig help text?
>>
>> Sure I can. Jonathan seem to have applied it so should I send a v2 or
>> a new patch?
>>
>
>He hasn't pushed things out yet, I think a v2 will be fine.
>
Yup a v2 is fine. Actually I regularly rebase this tree and it may eat babies! All work more or less should be against Greg's staging/staging-next tree as that is nice and non debasing.
>>>>> ---
>>>>> drivers/iio/Kconfig | 7 +++++++
>>>>> drivers/iio/Makefile | 2 ++
>>>>> 2 files changed, 9 insertions(+)
>>>>>
>>>>> diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
>>>>> index 9af763a..d1f06f2 100644
>>>>> --- a/drivers/iio/Kconfig
>>>>> +++ b/drivers/iio/Kconfig
>>>>> @@ -12,6 +12,13 @@ menuconfig IIO
>>>>>
>>>>> if IIO
>>>>>
>>>>> +config IIO_DEBUG
>>>>> + boolean "Debug support for Industrial I/O"
>>>>> + depends on DEBUG_KERNEL
>>>>> + help
>>>>> + Say "yes" to enable debug messaging (like dev_dbg and
>pr_debug),
>>>>> + sysfs, and debugfs support in Industrial I/O subsystem and
>drivers.
>>>
>>> This has nothing to do with either sysfs or debugfs support.
>>
>> Say "yes" to enable debug messaging (like dev_dbg and pr_debug)
>> support in Industrial I/O subsystem and drivers.
>>
>> ?
>>
>> --
>> Otavio Salvador O.S. Systems
>> http://www.ossystems.com.br http://projetos.ossystems.com.br
>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2013-07-16 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373898160-8460-1-git-send-email-otavio@ossystems.com.br>
2013-07-15 14:22 ` [PATCH 2/5] ARM: mxs-lradc: Simplify mxs_lradc_trigger_init error handle Otavio Salvador
2013-07-15 14:24 ` Marek Vasut
2013-07-15 14:38 ` Otavio Salvador
2013-07-15 23:00 ` Marek Vasut
2013-07-16 12:38 ` Otavio Salvador
2013-07-15 14:22 ` [PATCH 5/5] iio: add configuration option for debug support Otavio Salvador
2013-07-16 9:58 ` Jonathan Cameron
2013-07-16 10:26 ` Lars-Peter Clausen
2013-07-16 12:01 ` Otavio Salvador
2013-07-16 12:09 ` Lars-Peter Clausen
2013-07-16 16:11 ` Jonathan Cameron [this message]
2013-07-16 16:06 ` Jonathan Cameron
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=07271c08-5b24-4d86-8833-4ff2e15c8bed@email.android.com \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=otavio@ossystems.com.br \
/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