From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Flavio Suligoi <f.suligoi@asem.it>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Johan Hovold <johan@kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2] gpiolib: Disallow identical line names in the same chip
Date: Thu, 7 Jan 2021 12:12:49 +0200 [thread overview]
Message-ID: <CAHp75VdhorVKXxcppuK6t+yUMS0mcLp_0rOWg7bgiWviP2rkbw@mail.gmail.com> (raw)
In-Reply-To: <d04ed4ea7bfe4438947e05c86f031ed4@asem.it>
On Thu, Jan 7, 2021 at 12:03 PM Flavio Suligoi <f.suligoi@asem.it> wrote:
> > Flavio, perhaps one more rule to the gpio-line-names property has to
> > be added into documentation (Bart, same to DT docs?):
> > - names inside one chip must be unique
>
> ok, I'll add this rule
Thanks!
Main point for calling you is that you may tell that what you also
assumed when assigned line names in your case(s).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-01-07 10:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 8:27 [PATCH v2] gpiolib: Disallow identical line names in the same chip Linus Walleij
2021-01-05 17:29 ` Andy Shevchenko
2021-01-05 23:23 ` Linus Walleij
2021-01-06 10:09 ` Bartosz Golaszewski
2021-01-06 13:34 ` Andy Shevchenko
2021-01-06 14:25 ` Bartosz Golaszewski
2021-01-06 16:14 ` Andy Shevchenko
2021-01-07 10:03 ` R: " Flavio Suligoi
2021-01-07 10:12 ` Andy Shevchenko [this message]
2021-01-07 13:12 ` Flavio Suligoi
2021-01-08 10:40 ` Flavio Suligoi
2021-01-08 15:03 ` Andy Shevchenko
2021-01-07 10:45 ` Linus Walleij
2021-01-07 13:49 ` R: " Flavio Suligoi
2021-01-07 13:55 ` Geert Uytterhoeven
2021-01-08 14:39 ` R: " Flavio Suligoi
2021-01-08 14:41 ` Geert Uytterhoeven
2021-01-08 14:43 ` R: " Flavio Suligoi
2021-01-08 15:05 ` Andy Shevchenko
2021-01-15 14:30 ` Bartosz Golaszewski
[not found] ` <CAHp75Vd017YY8HU-Ai7jnQEJ4PEgiU4VXn-jhLBKwERmsG_5MA@mail.gmail.com>
2021-01-15 17:31 ` Geert Uytterhoeven
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=CAHp75VdhorVKXxcppuK6t+yUMS0mcLp_0rOWg7bgiWviP2rkbw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=f.suligoi@asem.it \
--cc=geert+renesas@glider.be \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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).