From: "Nigel Bennington" <nigel-home@corleco.com>
To: <axboe@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Broken source file in v2.4.7 sources
Date: Tue, 31 Jul 2001 18:47:40 +0100 [thread overview]
Message-ID: <NPEEKFLGNDBMBALCMAHGAEBBCBAA.nigel-home@corleco.com> (raw)
Hi, I hope I've addressed this bug report to the right people...
In the sources for v2.4.7, as current yesterday (30/Jun/2001), the file
drivers/block/DAC960.c
refers to the sem member of a variable defined as being of type IO_Request_T
tracking this backwards, it maps to the structure struct request, defined in
the file
include/linux/blkdev.h
this struct does not contain a member sem, although it did in v2.4.3 (the
only other kernel sources I have),
this means that the DAC960.c file is broken in the 2.4.7 kernel.
Hope this helps.
p.s. Is 2.4.7 considered a stable release, or should I be looking at
something between 2.4.3 and 2.4.7?
Thanks in advance,
Nigel Bennington.
next reply other threads:[~2001-07-31 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 17:47 Nigel Bennington [this message]
2001-07-31 18:25 ` Jens Axboe
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=NPEEKFLGNDBMBALCMAHGAEBBCBAA.nigel-home@corleco.com \
--to=nigel-home@corleco.com \
--cc=axboe@suse.de \
--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
all inboxes | Powered by JetHome®