From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org
Subject: [2.5 patch] small cleanup for include/linux/efs_fs.h
Date: Sun, 19 Jan 2003 00:34:01 +0100 [thread overview]
Message-ID: <20030118233401.GV10647@fs.tum.de> (raw)
The patch below includes the following small cleanups for
include/linux/efs_fs.h:
- remove unused #define MIN/MAX
- remove check for kernels < 2.2
I've tested the compilation with 2.5.59.
cu
Adrian
--- linux-2.5.59-full/include/linux/efs_fs.h.old 2003-01-19 00:27:21.000000000 +0100
+++ linux-2.5.59-full/include/linux/efs_fs.h 2003-01-19 00:27:56.000000000 +0100
@@ -15,14 +15,6 @@
#include <asm/uaccess.h>
-#ifndef LINUX_VERSION_CODE
-#include <linux/version.h>
-#endif
-
-#if LINUX_VERSION_CODE < 0x20200
-#error This code is only for linux-2.2 and later.
-#endif
-
/* 1 block is 512 bytes */
#define EFS_BLOCKSIZE_BITS 9
#define EFS_BLOCKSIZE (1 << EFS_BLOCKSIZE_BITS)
@@ -32,13 +24,6 @@
#include <linux/efs_fs_sb.h>
#include <linux/efs_dir.h>
-#ifndef MIN
-#define MIN(a, b) (((a) < (b)) ? (a) : (b))
-#endif
-#ifndef MAX
-#define MAX(a, b) (((a) > (b)) ? (a) : (b))
-#endif
-
static inline struct efs_inode_info *INODE_INFO(struct inode *inode)
{
return container_of(inode, struct efs_inode_info, vfs_inode);
reply other threads:[~2003-01-18 23:25 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=20030118233401.GV10647@fs.tum.de \
--to=bunk@fs.tum.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