From: Christoph Hellwig <hch@infradead.org>
To: GertJan Spoelman <kl@gjs.cc>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] via686a sensors support
Date: Sun, 12 Jan 2003 18:34:38 +0000 [thread overview]
Message-ID: <20030112183438.A13025@infradead.org> (raw)
In-Reply-To: <200301121925.14095.kl@gjs.cc>; from kl@gjs.cc on Sun, Jan 12, 2003 at 07:25:14PM +0100
> @@ -16,7 +16,7 @@
> while the kernel is running. If you want to compile it as a module,
> say M here and read <file:Documentation/modules.txt>.
>
> - The module will be called i2c-amd756.o.
> + The module will be called i2c-amd756.ko.
Please don't submit unrelated changes in this patch. While I agree with
this documentation fix it's clearly a separate issue.
> +#include <linux/version.h>
you don't need this header.
> +#ifndef PCI_DEVICE_ID_VIA_82C686_4
> +#define PCI_DEVICE_ID_VIA_82C686_4 0x3057
> +#endif
This one should be in include/linux/pci_ids.h
> +extern inline long IN_FROM_REG(u8 val, int inNum)
All these extern inlines should be static inline instead.
> +static int via686a_find(int *address)
> +{
> + u16 val;
> +
> + if (!pci_present())
> + return -ENODEV;
> +
> + if (!(s_bridge = pci_find_device(PCI_VENDOR_ID_VIA,
> + PCI_DEVICE_ID_VIA_82C686_4,
> + NULL)))
> + return -ENODEV;
I think this should converted to a 2.4/2.5-style PCI driver. See the
amd drivers.
> +/* No commands defined yet */
> +static int via686a_command(struct i2c_client *client, unsigned int cmd, void *arg)
> +{
> + return 0;
> +}
->command is optional, so there's no need to have this stub.
> +
> + if ((jiffies - data->last_updated > HZ + HZ / 2) ||
> + (jiffies < data->last_updated) || !data->valid) {
Use time_after here?
next prev parent reply other threads:[~2003-01-12 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 18:25 [PATCH] via686a sensors support GertJan Spoelman
2003-01-12 18:34 ` Christoph Hellwig [this message]
2003-01-14 22:50 ` GertJan Spoelman
2003-01-15 6:15 ` Christoph Hellwig
2003-01-16 20:37 ` GertJan Spoelman
2003-01-19 17:08 ` Pavel Machek
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=20030112183438.A13025@infradead.org \
--to=hch@infradead.org \
--cc=kl@gjs.cc \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox