From: Linus Walleij <linus.walleij@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] gpiolib: Disallow identical line names in the same chip
Date: Mon, 14 Dec 2020 23:39:50 +0100 [thread overview]
Message-ID: <CACRpkda5_JwCAB2TisyzdJgb395JmU1AfuDDX0gWTvEj7-Mamw@mail.gmail.com> (raw)
In-Reply-To: <X9cwahptmETQ5lkL@localhost>
On Mon, Dec 14, 2020 at 10:29 AM Johan Hovold <johan@kernel.org> wrote:
> As I mentioned earlier, the not-globally unique warning only makes sense
> for cases where all names comes from something like devicetree, and we
> shouldn't warn if we plug in two identical USB devices that provide
> default line names.
>
> Not sure it's even warranted to warn even if those default names collide
> with the names provided in devicetree. Perhaps best to just drop the
> flat-namespace assumption entirely and make sure gpiolib and the
> userspace library can handle that.
You're right. (As usual.)
I dropped the global collision warning when applying.
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-12-14 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 0:34 [PATCH] gpiolib: Disallow identical line names in the same chip Linus Walleij
2020-12-12 9:23 ` Geert Uytterhoeven
2020-12-12 12:51 ` Linus Walleij
2020-12-14 9:23 ` Johan Hovold
2020-12-13 15:00 ` Andy Shevchenko
2020-12-14 8:45 ` Bartosz Golaszewski
2020-12-14 9:17 ` Linus Walleij
2020-12-14 9:29 ` Johan Hovold
2020-12-14 22:39 ` Linus Walleij [this message]
2020-12-15 8:24 ` 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=CACRpkda5_JwCAB2TisyzdJgb395JmU1AfuDDX0gWTvEj7-Mamw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=johan@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.