From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v1 1/2] lib/cmdline: Export next_arg() for being used in modules
Date: Mon, 1 Mar 2021 18:59:31 +0200 [thread overview]
Message-ID: <20210301165932.62352-1-andriy.shevchenko@linux.intel.com> (raw)
At least one module will benefit from using next_arg() helper.
Let's export it for that module and others if they consider it
helpful.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
lib/cmdline.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/cmdline.c b/lib/cmdline.c
index 5d474c626e24..5546bf588780 100644
--- a/lib/cmdline.c
+++ b/lib/cmdline.c
@@ -272,3 +272,4 @@ char *next_arg(char *args, char **param, char **val)
/* Chew up trailing spaces. */
return skip_spaces(args);
}
+EXPORT_SYMBOL(next_arg);
--
2.30.1
next reply other threads:[~2021-03-01 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:59 Andy Shevchenko [this message]
2021-03-01 16:59 ` [PATCH v1 2/2] gpio: aggregator: Replace custom get_arg() with a generic next_arg() Andy Shevchenko
2021-03-02 16:09 ` Linus Walleij
2021-03-04 9:01 ` Geert Uytterhoeven
2021-03-04 10:58 ` Andy Shevchenko
2021-03-02 16:24 ` [PATCH v1 1/2] lib/cmdline: Export next_arg() for being used in modules Linus Walleij
2021-03-04 8:53 ` Geert Uytterhoeven
2021-03-04 10:59 ` Andy Shevchenko
2021-03-08 15:38 ` Bartosz Golaszewski
2021-03-08 16:36 ` Andy Shevchenko
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=20210301165932.62352-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 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).