From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] try to run MAKEDEV if i2c-dev device files are
Date: Sun, 08 Jul 2007 18:33:44 +0000 [thread overview]
Message-ID: <20070708203344.45b2b7f5@hyperion.delvare> (raw)
In-Reply-To: <20070707215305.6211e914@hyperion.delvare>
Hi Hans,
On Sun, 08 Jul 2007 07:54:29 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > First of all, a question: how many i2c device nodes does your MAKEDEV
> > create? The one I have in Slackware 9.1 only creates i2c-0 and i2c-1.
> > This might not be sufficient. Not our fault though.
>
> Mine version create i2c-0 - i2c-7
Much more reasonable.
> > Secondly, MAKEDEV was in /dev on Slackware, so maybe we could test both
> > locations?
>
> I had laready thought about that, as it used to be in /dev with Fedora / RH
> once too, but that was a long time ago. I thought al distro's would have fixed
> that by now.
>
> I'll add checking for and running of /dev/MAKEDEV to svn in a couple of minutes.
Good, thanks.
> > Then, the good news is that we should be able to drop the reference to
> > prog/mkdev/mkdev.sh, and finally delete it from the lm-sensors package
> > (in branch 3.0.0). I don't plan to move it to i2c-tools. On new systems
> > it's not needed. On old systems, MAKEDEV should do the work.
I've done that now.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2007-07-08 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 19:53 [lm-sensors] try to run MAKEDEV if i2c-dev device files are Jean Delvare
2007-07-08 5:54 ` [lm-sensors] try to run MAKEDEV if i2c-dev device files Hans de Goede
2007-07-08 18:33 ` Jean Delvare [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=20070708203344.45b2b7f5@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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.