From: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH]i2c-dev: add ioctls PROBE and REMOVE
Date: Fri, 27 Mar 2009 14:13:32 +0100 [thread overview]
Message-ID: <49CCD0FC.9030500@gmx.de> (raw)
In-Reply-To: <20090327134034.754908b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Jean Delvare said the following:
> Hi Michael,
>
> On Fri, 27 Mar 2009 11:19:27 +0100, Michael Lawnick wrote:
>> could you give it a look?
>> If you at least ACK the interface, I could do the patch for the
>> documentation.
>
> Come on, which part of "this should be implemented in sysfs" did you
> not understand? I'm a little tired of you trying to implement it using
> _all_ other possible ways except the one we agreed on. If you need this
> feature faster than I can implement it, please stick to the plan and
> implement it using sysfs. If not, then just stay quiet and wait for it
> to happen.
Huh - don't bite me!
This step I wanted to discuss next:
AFAICS I2C subsystem doesn't implement any sysFs-entry itself. They are
all either from client or device-driver system. I not even dared to ask
for a comment to this before adding the feature on i2c-dev, a way that
does not change the visible interface.
I can't wait too long for implementation on sysFs. I'm ready to do it
now, if we agree on the place where to create the entries, naming and
interface.
What is your time line?
Naming IMHO should be probe/remove, parameters could be
"<client-name>,<id>" / "<id>", just as done in i2c-dev implementation,
if created per adapter.
But where to place?
--
*Kind* regards,
Michael
next prev parent reply other threads:[~2009-03-27 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 8:59 [PATCH]i2c-dev: add ioctls PROBE and REMOVE Michael Lawnick
[not found] ` <49CB43E0.2050503-Mmb7MZpHnFY@public.gmane.org>
2009-03-27 10:19 ` Michael Lawnick
[not found] ` <49CCA82F.90106-Mmb7MZpHnFY@public.gmane.org>
2009-03-27 12:40 ` Jean Delvare
[not found] ` <20090327134034.754908b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-27 13:13 ` Michael Lawnick [this message]
[not found] ` <49CCD0FC.9030500-Mmb7MZpHnFY@public.gmane.org>
2009-03-27 13:57 ` Jean Delvare
[not found] ` <20090327145726.13c99aed-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-27 14:07 ` Jean Delvare
[not found] ` <20090327150716.094666d1-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-04-02 12:36 ` Michael Lawnick
[not found] ` <49D4B14B.50405-Mmb7MZpHnFY@public.gmane.org>
2009-04-07 10:15 ` Jean Delvare
[not found] ` <20090407121550.7d15bfae-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-04-07 12:17 ` Michael Lawnick
[not found] ` <49DB446A.2000705-Mmb7MZpHnFY@public.gmane.org>
2009-04-07 13:11 ` Jean Delvare
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=49CCD0FC.9030500@gmx.de \
--to=ml.lawnick-mmb7mzphnfy@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox