From: Bartosz Golaszewski <brgl@bgdev.pl>
To: "Joel Becker" <jlbec@evilplan.org>,
"Christoph Hellwig" <hch@lst.de>, "Shuah Khan" <shuah@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kent Gibson" <warthog618@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Jack Winch" <sunt.un.morcov@gmail.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v7 1/8] configfs: increase the item name length
Date: Fri, 8 Oct 2021 10:17:32 +0200 [thread overview]
Message-ID: <20211008081739.26807-2-brgl@bgdev.pl> (raw)
In-Reply-To: <20211008081739.26807-1-brgl@bgdev.pl>
20 characters limit for item name is relatively small. Let's increase it
to 32 to fit '04-committable-children' - a name we'll use in the sample
code for committable items.
Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
include/linux/configfs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/configfs.h b/include/linux/configfs.h
index 97cfd13bae51..e398fb2e83b2 100644
--- a/include/linux/configfs.h
+++ b/include/linux/configfs.h
@@ -25,7 +25,7 @@
#include <linux/kref.h> /* struct kref */
#include <linux/mutex.h> /* struct mutex */
-#define CONFIGFS_ITEM_NAME_LEN 20
+#define CONFIGFS_ITEM_NAME_LEN 32
struct module;
--
2.30.1
next prev parent reply other threads:[~2021-10-08 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 8:17 [PATCH v7 0/8] gpio: implement the configfs testing module Bartosz Golaszewski
2021-10-08 8:17 ` Bartosz Golaszewski [this message]
2021-10-08 8:17 ` [PATCH v7 2/8] configfs: use (1UL << bit) for internal flags Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 3/8] configfs: implement committable items Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 4/8] samples: configfs: add a committable group Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 5/8] gpio: sim: new testing module Bartosz Golaszewski
2021-10-18 10:40 ` Andy Shevchenko
2021-10-19 14:16 ` Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 6/8] selftests: gpio: provide a helper for reading chip info Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 7/8] selftests: gpio: add a helper for reading GPIO line names Bartosz Golaszewski
2021-10-08 8:17 ` [PATCH v7 8/8] selftests: gpio: add test cases for gpio-sim Bartosz Golaszewski
2021-10-15 14:13 ` [PATCH v7 0/8] gpio: implement the configfs testing module Bartosz Golaszewski
2021-10-16 22:23 ` Linus Walleij
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=20211008081739.26807-2-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sunt.un.morcov@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=warthog618@gmail.com \
/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).