From: Michael Lawnick <nospam_lawnick-Mmb7MZpHnFY@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH]i2c: Make test for force on client probe possible
Date: Fri, 20 Mar 2009 09:02:31 +0100 [thread overview]
Message-ID: <49C34D97.1010603@gmx.de> (raw)
In-Reply-To: <20090313130942.5addd79e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Sorry for the delay, had to fix a bug in u-boot...
Jean Delvare said the following:
> Hi Michael,
>
> I don't know how you sent this mail, but that's not OK. If you intend
> to do kernel development, you have to use a real e-mail addresses all
> along the way.
>
Discussed in PM.
> On Fri, 13 Mar 2009 11:15:57 +0100, Michael Lawnick wrote:
>> in new driver model 'kind' is no more provided for client's probe
>> function. The driver frame work creates the path
>> sys/bus/i2c/devices/[bus]-[dev]/ and populates it with the entries
>> modalias, name, subsystem@ and uevent. If probe fails (because the
>> device is not on bus at the moment) the client's sysFs-entries are not
>> created, but the entries above remain.
>
> This is correct, and this is by design. This is how the Linux device
> driver model works, BTW, nothing i2c-specific there.
>
Even if this is by (current linux) design, I think it is not ok ;-)
It leaves an inconsistent (not instable) system. IMHO either the entries
should be completely removed or completely created but not that half the
way.
Should we CC another list?
--
Regards,
Michael
next prev parent reply other threads:[~2009-03-20 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 10:15 [PATCH]i2c: Make test for force on client probe possible Michael Lawnick
[not found] ` <49BA325D.7030308-Mmb7MZpHnFY@public.gmane.org>
2009-03-13 12:09 ` Jean Delvare
[not found] ` <20090313130942.5addd79e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-20 8:02 ` Michael Lawnick [this message]
[not found] ` <49C34D97.1010603-Mmb7MZpHnFY@public.gmane.org>
2009-03-20 8:44 ` 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=49C34D97.1010603@gmx.de \
--to=nospam_lawnick-mmb7mzphnfy@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