From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
Stephen Warren <swarren@nvidia.com>,
Mike Frysinger <vapier.adi@gmail.com>,
Linus Walleij <linus.ml.walleij@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Barry Song <21cnbao@gmail.com>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
Russell King <linux@arm.linux.org.uk>,
Linaro Dev <linaro-dev@lists.linaro.org>,
Lee Jones <lee.jones@linaro.org>,
David Brown <davidb@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Stijn Devriendt <highguy@gmail.com>
Subject: Re: [PATCH] drivers: create a pin control subsystem v8
Date: Tue, 25 Oct 2011 09:23:35 +0100 [thread overview]
Message-ID: <20111025082334.GA21616@sirena.org.uk> (raw)
In-Reply-To: <20111025081719.GA4605@ponder.secretlab.ca>
On Tue, Oct 25, 2011 at 10:17:19AM +0200, Grant Likely wrote:
> I've got no issue with a debugfs interface, although it would probably
> a good idea to put a big scary warning into klog when userspace starts
> manipulating pinctrl setting. Maybe should taint the kernel too.
Yes, we really should taint the kernel for any non-mediated interface -
never mind instability this stuff can cause physical damage if you get
it wrong.
next prev parent reply other threads:[~2011-10-25 8:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 12:03 [PATCH] drivers: create a pin control subsystem v8 Linus Walleij
2011-09-30 2:07 ` Grant Likely
2011-09-30 15:05 ` Linus Walleij
2011-09-30 17:07 ` Grant Likely
2011-09-30 17:20 ` Linus Walleij
2011-10-01 10:39 ` Linus Walleij
2011-10-04 20:35 ` Grant Likely
2011-10-22 17:44 ` Mike Frysinger
2011-10-24 7:26 ` Linus Walleij
2011-10-24 7:36 ` Grant Likely
2011-10-24 7:48 ` Linus Walleij
2011-10-24 9:20 ` Mike Frysinger
2011-10-24 12:28 ` Linus Walleij
2011-10-24 11:05 ` Grant Likely
2011-10-25 8:05 ` Tony Lindgren
2011-10-25 8:17 ` Grant Likely
2011-10-25 8:23 ` Mark Brown [this message]
2011-10-24 9:14 ` Mike Frysinger
2011-09-30 18:08 ` Stephen Warren
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=20111025082334.GA21616@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=davidb@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=highguy@gmail.com \
--cc=joe@perches.com \
--cc=lee.jones@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=swarren@nvidia.com \
--cc=tony@atomide.com \
--cc=vapier.adi@gmail.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