From: "Simon Turvey" <turveysp@ntlworld.com>
To: <linux-kernel@vger.kernel.org>
Subject: Modifying file_operations
Date: Thu, 13 Sep 2001 23:53:45 +0100 [thread overview]
Message-ID: <003201c13ca6$f1aeffa0$020ba8c0@theflat.net> (raw)
Warning! This might be a stupid question.
Is it safe to modify the read() entry of a driver's file_operations struct
in order to modify the behaviour of the driver depending upon some context,
say a particular hardware mode. Or is the only way to do this safely to
test the current mode in read() adding overhead to the function.
Ta,
Simon
reply other threads:[~2001-09-13 22:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='003201c13ca6$f1aeffa0$020ba8c0@theflat.net' \
--to=turveysp@ntlworld.com \
--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