From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Dario Binacchi <dariobin@libero.it>
Cc: Drew Fustini <drew@beagleboard.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 1/2] pinctrl: core: configure pinmux from pins debug file
Date: Tue, 18 May 2021 17:01:30 +0300 [thread overview]
Message-ID: <CAHp75VeADiRKdfnsXQ=y3z1WAJBbtZ+P=8tdyYtVQpJrSrQ63Q@mail.gmail.com> (raw)
In-Reply-To: <1735504854.166374.1621346262270@mail1.libero.it>
On Tue, May 18, 2021 at 4:57 PM Dario Binacchi <dariobin@libero.it> wrote:
> > Il 17/05/2021 22:02 Andy Shevchenko <andy.shevchenko@gmail.com> ha scritto:
> > On Sun, May 16, 2021 at 7:43 PM Dario Binacchi <dariobin@libero.it> wrote:
...
> > Can't you use strncpy_from_user() ?
>
> Ok, I'll use strncpy_from_user() in the next version of the patch
Don't be in a hurry.
We need to settle down the interface first. We still haven't heard
from the maintainer (Linus?) about it. Neither we have a clear view if
we need to revert that patch that dropped pinconf-config (Drew, what
do you think?).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-05-18 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 13:55 [PATCH 0/2] am335x: set pinmux registers from pins debug file Dario Binacchi
2021-05-16 13:55 ` [PATCH 1/2] pinctrl: core: configure pinmux " Dario Binacchi
2021-05-17 20:02 ` Andy Shevchenko
2021-05-17 22:57 ` Drew Fustini
2021-05-18 9:38 ` Dario Binacchi
2021-05-18 10:21 ` Drew Fustini
2021-05-18 10:41 ` Andy Shevchenko
2021-05-18 13:57 ` Dario Binacchi
2021-05-18 14:01 ` Andy Shevchenko [this message]
2021-05-19 10:02 ` Drew Fustini
2021-05-19 11:27 ` Andy Shevchenko
2021-05-20 4:17 ` Drew Fustini
2021-05-20 8:10 ` Andy Shevchenko
2021-05-16 13:55 ` [PATCH 2/2] pinctrl: single: set " Dario Binacchi
2021-05-17 5:57 ` Tony Lindgren
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='CAHp75VeADiRKdfnsXQ=y3z1WAJBbtZ+P=8tdyYtVQpJrSrQ63Q@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=dariobin@libero.it \
--cc=drew@beagleboard.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;
as well as URLs for NNTP newsgroup(s).