From: Jeff Garzik <jeff@garzik.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] [SCSI] gdth: misc cleanups, preparation for ISA/EISA hotplug API
Date: Sun, 24 Feb 2008 00:18:23 -0500 [thread overview]
Message-ID: <47C0FE1F.300@garzik.org> (raw)
In-Reply-To: <20080224045810.GA17051@infradead.org>
Christoph Hellwig wrote:
> Eventually we shoud just kill the INT_COAL ifdefed code. It has never
> been enabled and clutters up the driver quite badly.
Noted (queued)... fine by me, and makes life easier.
>> +#ifdef CONFIG_EISA
>> + if ((ha->type == GDT_EISA) && (ha->ccb_phys))
>> + pci_unmap_single(ha->pdev, ha->ccb_phys, sizeof(gdth_cmd_str),
>> + PCI_DMA_BIDIRECTIONAL);
>> +#endif /* CONFIG_EISA */
>
> I don't think moving this into the common helper makes any sense, as
> it's only ever done for the eisa adapter. Just keep it local there.
>
>> +#ifdef CONFIG_EISA
>> + if (ha->type == GDT_EISA) {
>> + ha->ccb_phys = pci_map_single(ha->pdev, &ha->cmdext,
>> + sizeof(gdth_cmd_str), PCI_DMA_BIDIRECTIONAL);
>> + if (!ha->ccb_phys)
>> + goto out_free;
>> + }
>> +#endif /* CONFIG_EISA */
>
> Same here.
hmmmmm. We'll see how it plays out... on the remove side, the above is
exact what happens in gdth_remove_one() without my patch, thus
consolidating two cases of the same code into one. There is a
less-strong argument for doing the allocation that way, but it may turn
out to be useful anyway once the ISA/EISA API conversion is complete.
Jeff
next prev parent reply other threads:[~2008-02-24 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 4:44 [PATCH 1/1] [SCSI] gdth: misc cleanups, preparation for ISA/EISA hotplug API Jeff Garzik
2008-02-24 4:58 ` Christoph Hellwig
2008-02-24 5:18 ` Jeff Garzik [this message]
2008-02-24 5:31 ` Christoph Hellwig
2008-02-24 5:34 ` Jeff Garzik
2008-02-24 6:37 ` Matthew Wilcox
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=47C0FE1F.300@garzik.org \
--to=jeff@garzik.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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