From: Guangyu Fang <gfang@mylex.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] block_device_operations
Date: Tue, 16 May 2000 21:12:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205087@msgid-missing> (raw)
Hi,
I'm using TurboLinux 2.3.99-pre6-000501-18. Since <linux/fs.h> has the
following definition:
struct block_device_operations {
int (*open) (struct inode *, struct file *);
int (*release) (struct inode *, struct file *);
int (*ioctl) (struct inode *, struct file *, unsigned, unsigned
long);
int (*check_media_change) (kdev_t);
int (*revalidate) (kdev_t);
};
Does it mean that block device can not do read/write operations? Is there
any work around?
Thanks.
Gary
next reply other threads:[~2000-05-16 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 21:12 Guangyu Fang [this message]
2000-05-16 22:12 ` [Linux-ia64] block_device_operations David Mosberger
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=marc-linux-ia64-105590678205087@msgid-missing \
--to=gfang@mylex.com \
--cc=linux-ia64@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