From: Adrian Bunk <bunk@stusta.de>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: Re: drivers/w1/: why is dscore.c not ds9490r.c ?
Date: Mon, 22 Nov 2004 14:33:44 +0100 [thread overview]
Message-ID: <20041122133344.GA19419@stusta.de> (raw)
In-Reply-To: <1101108672.2843.55.camel@uganda>
On Mon, Nov 22, 2004 at 10:31:12AM +0300, Evgeniy Polyakov wrote:
> On Mon, 2004-11-22 at 01:02, Adrian Bunk wrote:
> > Hi Evgeniy,
>
> Hello, Adrian.
Hi Evgeniy,
> > drivers/w1/Makefile in recent 2.6 kernels contains:
> > obj-$(CONFIG_W1_DS9490) += ds9490r.o
> > ds9490r-objs := dscore.o
> >
> > Is there a reason, why dscore.c isn't simply named ds9490r.c ?
>
> dscore.c is a core function set to work with ds2490 chip.
> ds9490* is built on top of it.
> Any vendor can create it's own w1 bus master using this chip,
> not ds9490.
if it was built on top of it, I'd have expected ds9490r.o to contain
additional object files.
How would a different w1 bus master chip look like in
drivers/w1/Makefile?
> Evgeniy Polyakov
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-11-22 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 22:02 drivers/w1/: why is dscore.c not ds9490r.c ? Adrian Bunk
2004-11-22 7:31 ` Evgeniy Polyakov
2004-11-22 13:33 ` Adrian Bunk [this message]
2004-11-22 16:25 ` Evgeniy Polyakov
2004-11-22 16:51 ` Adrian Bunk
2004-11-22 17:05 ` Evgeniy Polyakov
2004-11-22 17:19 ` Adrian Bunk
2004-11-22 17:37 ` Evgeniy Polyakov
2004-11-23 0:20 ` Adrian Bunk
2004-11-23 10:34 ` Evgeniy Polyakov
2004-11-25 15:56 ` Adrian Bunk
2004-11-29 1:52 ` [2.6 patch] drivers/w1/: possible cleanups Adrian Bunk
2004-11-29 5:12 ` Evgeniy Polyakov
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=20041122133344.GA19419@stusta.de \
--to=bunk@stusta.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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