From: Flameeyes <dgp85@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: (Resent) [PATCH] 2.5.72 smb_proc_setattr_unix warnings
Date: 19 Jun 2003 14:20:58 +0200 [thread overview]
Message-ID: <1056025258.940.6.camel@laurelin> (raw)
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
This patch fixes these warnings:
CC fs/smbfs/proc.o
fs/smbfs/proc.c: In function `smb_proc_setattr_unix':
fs/smbfs/proc.c:3044: warning: integer constant is too large for "long"
type
fs/smbfs/proc.c:3045: warning: integer constant is too large for "long"
type
fs/smbfs/proc.c:3046: warning: integer constant is too large for "long"
type
fs/smbfs/proc.c:3047: warning: integer constant is too large for "long"
type
fs/smbfs/proc.c:3048: warning: integer constant is too large for "long"
type
it simply adds the ULL attr at the end of the constants in
include/linux/smbno.h
--
Flameeyes <dgp85@users.sf.net>
[-- Attachment #2: patch-smb.diff --]
[-- Type: text/plain, Size: 525 bytes --]
--- include/linux/smbno.h.orig 2003-06-17 13:11:22.000000000 +0200
+++ include/linux/smbno.h 2003-06-17 13:11:38.000000000 +0200
@@ -347,8 +347,8 @@
#define SMB_MODE_NO_CHANGE 0xFFFFFFFF
#define SMB_UID_NO_CHANGE 0xFFFFFFFF
#define SMB_GID_NO_CHANGE 0xFFFFFFFF
-#define SMB_TIME_NO_CHANGE 0xFFFFFFFFFFFFFFFF
-#define SMB_SIZE_NO_CHANGE 0xFFFFFFFFFFFFFFFF
+#define SMB_TIME_NO_CHANGE 0xFFFFFFFFFFFFFFFFULL
+#define SMB_SIZE_NO_CHANGE 0xFFFFFFFFFFFFFFFFULL
/* UNIX filetype mappings. */
#define UNIX_TYPE_FILE 0
next reply other threads:[~2003-06-19 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 12:20 Flameeyes [this message]
2003-06-19 17:32 ` (Resent) [PATCH] 2.5.72 smb_proc_setattr_unix warnings Joshua Kwan
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=1056025258.940.6.camel@laurelin \
--to=dgp85@users.sourceforge.net \
--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