From: Ken Brownfield <brownfld@irridia.com>
To: MIDN Sean Jones <m053546@usna.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible bugs
Date: Tue, 4 Dec 2001 00:19:57 -0600 [thread overview]
Message-ID: <20011204001957.A31869@asooo.flowerfire.com> (raw)
In-Reply-To: <1007332194.11790.0.camel@Eagle.usna.edu>
In-Reply-To: <1007332194.11790.0.camel@Eagle.usna.edu>; from m053546@usna.edu on Sun, Dec 02, 2001 at 05:29:52PM -0500
There was a patch sent a month or so ago that removed disable_ida_dma.
I usually apply cleanups like this, but it's a toss-up whether it's
worth it. Maybe these functions should be removed from 2.5 until
someone complains.
--
Ken.
brownfld@irridia.com
On Sun, Dec 02, 2001 at 05:29:52PM -0500, MIDN Sean Jones wrote:
| I was looking for code to cleanup and found these warnings:
|
| (from 2.4.17-pre2)
|
| dmi_scan.c:195: warning: `disable_ide_dma' defined but not used
| agpgart_be.c:524: warning: `agp_generic_create_gatt_table' defined but
| not used
| agpgart_be.c:652: warning: `agp_generic_free_gatt_table' defined but not
| used
| agpgart_be.c:700: warning: `agp_generic_insert_memory' defined but not
| used
| agpgart_be.c:758: warning: `agp_generic_remove_memory' defined but not
| used
| parport_pc.c:1784: warning: `parport_ECP_supported' defined but not used
|
| Are these functions supposed to be there or are they leftovers from
| previous modifications.
|
| Thanks,
|
| Sean Jones
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-12-04 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 22:29 Possible bugs MIDN Sean Jones
2001-12-04 6:19 ` Ken Brownfield [this message]
[not found] <200112041201.fB4C14d23225@lists.us.dell.com>
2001-12-04 14:33 ` Bill Crawford
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=20011204001957.A31869@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m053546@usna.edu \
/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