From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Kent Gibson <warthog618@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v9 1/1] gpio: add sloppy logic analyzer using polling
Date: Thu, 13 Jun 2024 15:51:59 +0200 [thread overview]
Message-ID: <CAMRc=Mem6HN13FOA_Ru8zC-GqGGLTsQiktLWs5bN4JD1aM3gHQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYtLDA3518uSYiTpu1PJuqNErHr9YMAKuar0CeFbfECPA@mail.gmail.com>
On Thu, Jun 13, 2024 at 3:47 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Thu, Jun 13, 2024 at 11:43 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> > To prove this point, I even moved the gpio-virtuser driver I'm working
> > on to drivers/misc/ too as it isn't a GPIO provider either and merely
> > a GPIO consumer with a one-shot user-space interface not conforming to
> > any standards.
>
> We *could* just create drivers/gpio/consumers/* and an entry into the
> top-level drivers/Kconfig to have those appear right under the GPIO
> providers...
>
> Yours,
> Linus Walleij
That would just add to confusion. GPIO consumers are all over the tree
after all.
Whatever, let's keep it in drivers/gpio/. Greg KH just shot down my
idea of putting gpio-virtuser in drivers/misc/.
Bart
next prev parent reply other threads:[~2024-06-13 13:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 11:26 [PATCH v9 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2024-06-10 11:26 ` [PATCH v9 1/1] gpio: add sloppy " Wolfram Sang
2024-06-10 14:30 ` Andy Shevchenko
2024-06-12 10:03 ` Wolfram Sang
2024-06-11 20:03 ` Bartosz Golaszewski
2024-06-12 16:03 ` Wolfram Sang
2024-06-13 8:17 ` Bartosz Golaszewski
2024-06-13 8:27 ` Linus Walleij
2024-06-13 8:50 ` Arnd Bergmann
2024-06-13 9:43 ` Bartosz Golaszewski
2024-06-13 11:48 ` Wolfram Sang
2024-06-13 13:47 ` Linus Walleij
2024-06-13 13:51 ` Bartosz Golaszewski [this message]
2024-06-13 14:20 ` Arnd Bergmann
2024-06-14 10:03 ` Wolfram Sang
2024-06-14 11:58 ` Arnd Bergmann
2024-06-14 12:14 ` Linus Walleij
2024-06-16 16:04 ` Wolfram Sang
2024-06-18 9:23 ` Wolfram Sang
2024-06-18 12:50 ` Bartosz Golaszewski
2024-06-18 16:09 ` Wolfram Sang
2024-06-18 18:58 ` Geert Uytterhoeven
2024-06-18 19:46 ` Bartosz Golaszewski
2024-06-13 15:04 ` Geert Uytterhoeven
2024-06-13 16:33 ` Wolfram Sang
2024-06-13 8:30 ` Linus Walleij
2024-06-13 11:45 ` Wolfram Sang
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='CAMRc=Mem6HN13FOA_Ru8zC-GqGGLTsQiktLWs5bN4JD1aM3gHQ@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=warthog618@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
/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).