From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 1/2] lib/cmdline: Export next_arg() for being used in modules
Date: Mon, 8 Mar 2021 18:36:47 +0200 [thread overview]
Message-ID: <YEZSn7VwhGEa4a6I@smile.fi.intel.com> (raw)
In-Reply-To: <CAMpxmJWz+iEqC77ORCQ-tHHc0SiHCPoOR0VR=Te4LXBfMoCPng@mail.gmail.com>
On Mon, Mar 08, 2021 at 04:38:42PM +0100, Bartosz Golaszewski wrote:
> On Thu, Mar 4, 2021 at 12:01 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Mar 04, 2021 at 09:53:28AM +0100, Geert Uytterhoeven wrote:
> > > On Mon, Mar 1, 2021 at 6:00 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > 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>
> > >
> > > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > Thanks Geert and Linus!
> >
> > Bart, do you want me to add it to my usual PR or you want to take it yourself
> > (I have no dependencies in my tree on this anyway)?
>
> Please send it with your PR.
Will do, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-03-08 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:59 [PATCH v1 1/2] lib/cmdline: Export next_arg() for being used in modules Andy Shevchenko
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 [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=YEZSn7VwhGEa4a6I@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert@linux-m68k.org \
--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