From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Chew <achew@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.8-rc2] sata_nv.c
Date: Tue, 27 Jul 2004 13:07:07 -0400 [thread overview]
Message-ID: <41068BBB.3090000@pobox.com> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B03F95E1@hqemmail02.nvidia.com>
Andrew Chew wrote:
> This patch updates the NVIDIA libata-based SATA driver to support the
> CK804 SATA controller.
Please fix and resubmit:
1) [style] no need to explicitly init first enum to zero:
+typedef enum
+{
+ NFORCE2 = 0,
+ NFORCE3,
+ CK804
+} nv_host_type_t;
2) in Linux (and POSIX), 'struct foo' is preferred over 'foo_t':
+{
+ nv_host_type_t host_type;
+ unsigned long host_flags;
+ void (*enable_hotplug)(struct ata_probe_ent
*probe_en
t);
+ void (*disable_hotplug)(struct ata_host_set
*host_set
);
+ void (*check_hotplug)(struct ata_host_set
*host_set);
+
+} nv_host_desc_t;
3) [style] single statements should not be enclosed by braces
+ if (host->host_desc->check_hotplug) {
+ host->host_desc->check_hotplug(host_set);
}
...
+ if (host->host_desc->host_flags & NV_HOST_FLAGS_SCR_MMIO) {
+ return readl(ap->ioaddr.scr_addr + (sc_reg * 4));
+ } else {
+ return inl(ap->ioaddr.scr_addr + (sc_reg * 4));
+ }
...
+ // Enable hotplug event interrupts.
+ if (host->host_desc->enable_hotplug) {
+ host->host_desc->enable_hotplug(probe_ent);
+ }
etc.
4) [leak] driver appears to be missing a ->host_free hook, to free your
nv_host_t structure.
+ host = kmalloc(sizeof(nv_host_t), GFP_KERNEL);
5) [bug] check ioremap return value for failure (==NULL)
+ mmio_base = ioremap(pci_resource_start(pdev, 5),
+ pci_resource_len(pdev, 5));
6) [leak] probe_ent->mmio_base is not set for the MMIO case, therefore,
iounmap() is never called for you by ata_pci_remove_one() [libata-core.c].
7) don't use host->scr_addr as a sly way to obtain your base address.
Use host_set->mmio_base directly (casting from unsigned long if it's PIO
rather than MMIO).
8) "avoid magic numbers". Avoid decimal or hexidecimal constants in
actual code. Prefer to use macros/enums instead.
+ pci_read_config_byte(probe_ent->pdev, 0x50, ®val);
+ regval |= 0x04;
+ pci_write_config_byte(probe_ent->pdev, 0x50, regval);
next prev parent reply other threads:[~2004-07-27 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 21:38 [PATCH 2.6.8-rc2] sata_nv.c Andrew Chew
2004-07-22 21:38 ` Andrew Chew
2004-07-27 17:07 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 18:45 Andrew Chew
2004-07-27 18:45 ` Andrew Chew
2004-07-27 18:55 ` Jeff Garzik
2004-07-27 20:26 Andrew Chew
2004-07-27 20:26 ` Andrew Chew
2004-08-05 21:31 Andrew Chew
2004-08-05 21:31 ` Andrew Chew
2004-08-05 21:53 ` Jeff Garzik
2004-08-05 22:06 Andrew Chew
2004-08-05 22:06 ` Andrew Chew
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=41068BBB.3090000@pobox.com \
--to=jgarzik@pobox.com \
--cc=achew@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--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 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.