public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <wdebruij@dds.nl>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][MINOR] define default SEEK_SET, SEEK_CUR and SEEK_END
Date: Mon, 5 Apr 2004 10:27:12 +0000	[thread overview]
Message-ID: <200404051027.13149.wdebruij@dds.nl> (raw)

this is a very minor patch to include the various llseek SEEK macro's into 
linux/fs.h

perhaps there's a reason this hasn't been included yet, but a simple grep 
showed me that I'm not the only one defining these in my drivers (which IMHO 
is bad). I simply copied these lines from libc's fnctl.h, including the 
original commentary. 

By the way, can someone tell me if I should cc: these minor patches to a 
specific maintainer? 

-- 
Willem de Bruijn
+31 6 2695 2446
+31 71 517 7174
wdebruij_at_dds.nl
http://www.wdebruij.dds.nl/

current project : 
Fairly Fast Packet Filter (FFPF)
http:/ffpf.sourceforge.net/

--- start of patch ---

diff -Nur linux-2.6.5-orig/include/linux/fs.h linux-2.6.5/include/linux/fs.h
--- linux-2.6.5-orig/include/linux/fs.h	2004-04-05 10:05:20.000000000 +0000
+++ linux-2.6.5/include/linux/fs.h	2004-04-05 10:08:54.934203912 +0000
@@ -87,6 +87,10 @@
 #define SEL_OUT		2
 #define SEL_EX		4
 
+#define SEEK_SET	0	/* Seek from beginning of file.  */
+#define SEEK_CUR	1	/* Seek from current position.  */
+#define SEEK_END	2	/* Seek from end of file.  */
+
 /* public flags for file_system_type */
 #define FS_REQUIRES_DEV 1 
 #define FS_BINARY_MOUNTDATA 2

-- 
Dit bericht is gescand op virussen en andere gevaarlijke inhoud door ULCN MailScanner en het bericht lijkt schoon te zijn.
This message has been scanned for viruses and dangerous content by ULCN MailScanner, and is believed to be clean.


                 reply	other threads:[~2004-04-05 10:26 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=200404051027.13149.wdebruij@dds.nl \
    --to=wdebruij@dds.nl \
    --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