From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Benoît Coussno" <b-cousson@ti.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Sourav Poddar" <sourav.poddar@ti.com>,
"Russ Dill" <Russ.Dill@ti.com>, "Felipe Balbi" <balbi@ti.com>,
"Koen Kooi" <koen@circuitco.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: Platform device tester - Allow removal
Date: Tue, 13 Aug 2013 11:20:12 -0700 [thread overview]
Message-ID: <20130813182012.GE7740@kroah.com> (raw)
In-Reply-To: <1376386470-27328-1-git-send-email-panto@antoniou-consulting.com>
On Tue, Aug 13, 2013 at 12:34:30PM +0300, Pantelis Antoniou wrote:
> This is a very simple device that allows testing of the removal path
> for platform devices.
>
> The only interface is a single writeable sysfs attribute (action).
Why not use the existing "unbind/bind" sysfs files that all busses
support? That's what userspace is expecting to use for adding and
removing devices from drivers from userspace.
This is a per-driver flag that the function platform_driver_probe() sets
for all platform drivers in the first line of that function. Remove
that line and see what happens :)
thanks,
greg k-h
next parent reply other threads:[~2013-08-13 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376386470-27328-1-git-send-email-panto@antoniou-consulting.com>
2013-08-13 18:20 ` Greg Kroah-Hartman [this message]
2013-08-13 18:42 ` [PATCH] staging: Platform device tester - Allow removal Pantelis Antoniou
2013-08-13 18:55 ` Russell King - ARM Linux
2013-08-13 19:33 ` Kevin Hilman
2013-08-13 18:55 ` Greg Kroah-Hartman
2013-08-13 18:59 ` Pantelis Antoniou
2013-08-13 19:02 ` Russell King - ARM Linux
2013-08-13 19:04 ` Pantelis Antoniou
2013-08-13 19:04 ` Greg Kroah-Hartman
2013-08-13 19:25 ` Kevin Hilman
2013-08-13 18:22 ` Greg Kroah-Hartman
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=20130813182012.GE7740@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Russ.Dill@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=koen@circuitco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=panto@antoniou-consulting.com \
--cc=paul@pwsan.com \
--cc=sourav.poddar@ti.com \
--cc=tony@atomide.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 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.