From: Tony Lindgren <tony@atomide.com>
To: Drew Fustini <drew@beagleboard.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Jason Kridner <jkridner@beagleboard.org>,
Robert Nelson <robertcnelson@beagleboard.org>,
Joe Perches <joe@perches.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 0/3] pinctrl: pinmux: Add pinmux-select debugfs file
Date: Wed, 17 Feb 2021 15:53:46 +0200 [thread overview]
Message-ID: <YC0f6uuNlbv7wjyP@atomide.com> (raw)
In-Reply-To: <20210216224455.1504008-1-drew@beagleboard.org>
* Drew Fustini <drew@beagleboard.org> [210216 22:46]:
> This series first converts the debugfs files in the pinctrl subsystem to
> octal permissions and then adds a new debugfs file "pinmux-select".
>
> Function name and group name can be written to "pinmux-select" which
> will cause the function and group to be activated on the pin controller.
Nice to see this happening!
Reviewed-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2021-02-17 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 22:44 [PATCH v6 0/3] pinctrl: pinmux: Add pinmux-select debugfs file Drew Fustini
2021-02-16 22:44 ` [PATCH v6 1/3] pinctrl: use to octal permissions for debugfs files Drew Fustini
2021-02-16 22:44 ` [PATCH v6 2/3] pinctrl: pinmux: Add pinmux-select debugfs file Drew Fustini
2021-02-17 10:10 ` Andy Shevchenko
2021-02-16 22:44 ` [PATCH v6 3/3] docs/pinctrl: document debugfs files Drew Fustini
2021-02-17 10:16 ` Andy Shevchenko
2021-02-17 13:53 ` Tony Lindgren [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=YC0f6uuNlbv7wjyP@atomide.com \
--to=tony@atomide.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@oracle.com \
--cc=drew@beagleboard.org \
--cc=geert@linux-m68k.org \
--cc=jkridner@beagleboard.org \
--cc=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robertcnelson@beagleboard.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.