From: Stephane Ouellette <ouellettes@videotron.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.4.22-rc1-ac1 Missing declaration in include/linux/proc_fs.h
Date: Sat, 09 Aug 2003 00:27:31 -0400 [thread overview]
Message-ID: <3F347833.2@videotron.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Folks,
the following patch fixes a compile warning about the implicit
declaration of proc_mkdir_mode() in proc_tty.c.
The patch applies against 2.4.22-rc1-ac1.
There is no such function (proc_mkdir_mode()) in 2.6.0-test2, so
the patch does not apply to it.
Stephane Ouellette.
[-- Attachment #2: proc_fs.h-2.4.22-rc1-ac1.diff --]
[-- Type: text/plain, Size: 1182 bytes --]
--- linux-2.4.22-rc1-ac1-orig/include/linux/proc_fs.h Fri Aug 8 22:47:38 2003
+++ linux-2.4.22-rc1-ac1-fixed/include/linux/proc_fs.h Sat Aug 9 00:11:16 2003
@@ -143,6 +143,8 @@
extern struct proc_dir_entry *proc_mknod(const char *,mode_t,
struct proc_dir_entry *,kdev_t);
extern struct proc_dir_entry *proc_mkdir(const char *,struct proc_dir_entry *);
+extern struct proc_dir_entry *proc_mkdir_mode(const char *name, mode_t mode,
+ struct proc_dir_entry *parent);
static inline struct proc_dir_entry *create_proc_read_entry(const char *name,
mode_t mode, struct proc_dir_entry *base,
@@ -192,7 +194,9 @@
static inline struct proc_dir_entry *proc_mknod(const char *name,mode_t mode,
struct proc_dir_entry *parent,kdev_t rdev) {return NULL;}
static inline struct proc_dir_entry *proc_mkdir(const char *name,
- struct proc_dir_entry *parent) {return NULL;}
+ struct proc_dir_entry *parent) {return NULL;}
+static inline struct proc_dir_entry *proc_mkdir_mode(const char *name,
+ mode_t mode, struct proc_dir_entry *parent) {return NULL;}
static inline struct proc_dir_entry *create_proc_read_entry(const char *name,
mode_t mode, struct proc_dir_entry *base,
reply other threads:[~2003-08-09 4:30 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=3F347833.2@videotron.ca \
--to=ouellettes@videotron.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.