From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] iio: tools: generic_buffer: increase trigger length
Date: Sun, 7 May 2017 16:03:01 +0100 [thread overview]
Message-ID: <c02626ec-4580-ef36-3b38-535e18531473@kernel.org> (raw)
In-Reply-To: <1493900000-26220-4-git-send-email-eugen.hristev@microchip.com>
On 04/05/17 13:13, Eugen Hristev wrote:
> Increased trigger length to 64 in order to cope with trigger names
> like fc030000.adc-dev0-external-rising
>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
Might as well change this now.
Applied to the togreg branch of iio.git.
Thanks,
Jonathan
> ---
> Changes in v2:
> - Modified trigger name length to 64
>
> tools/iio/iio_utils.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/iio/iio_utils.h b/tools/iio/iio_utils.h
> index 780f201..8b379da 100644
> --- a/tools/iio/iio_utils.h
> +++ b/tools/iio/iio_utils.h
> @@ -13,7 +13,7 @@
> #include <stdint.h>
>
> /* Made up value to limit allocation sizes */
> -#define IIO_MAX_NAME_LENGTH 30
> +#define IIO_MAX_NAME_LENGTH 64
>
> #define FORMAT_SCAN_ELEMENTS_DIR "%s/scan_elements"
> #define FORMAT_TYPE_FILE "%s_type"
>
prev parent reply other threads:[~2017-05-07 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:13 [PATCH v2 0/3] iio: adc: sama5d2_adc hw triggers and buffers Eugen Hristev
2017-05-04 12:13 ` [PATCH v2 1/3] ARM: dts: at91: sama5d2_xplained: enable ADTRG pin Eugen Hristev
2017-05-04 12:13 ` [PATCH v2 2/3] iio: adc: at91-sama5d2_adc: add hw trigger and buffer support Eugen Hristev
2017-05-07 15:01 ` Jonathan Cameron
2017-05-10 8:49 ` Eugen Hristev
2017-05-11 6:09 ` Ludovic Desroches
2017-05-14 15:12 ` Jonathan Cameron
2017-05-15 7:38 ` Eugen Hristev
2017-05-16 18:03 ` Jonathan Cameron
2017-05-17 7:47 ` Peter Rosin
2017-05-17 11:35 ` Eugen Hristev
2017-05-21 11:58 ` Jonathan Cameron
2017-05-04 12:13 ` [PATCH v2 3/3] iio: tools: generic_buffer: increase trigger length Eugen Hristev
2017-05-07 15:03 ` 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=c02626ec-4580-ef36-3b38-535e18531473@kernel.org \
--to=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).