From: "Björn JACKE" <bjacke-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] CIFS: fix mapping of SFM_SPACE and SFM_PERIOD
Date: Thu, 4 May 2017 00:06:32 +0200 [thread overview]
Message-ID: <20170503220632.GA20285@SerNet.DE> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 92 bytes --]
Hi,
please review and apply to current and long-term kernels like 4.9, please.
Björn
[-- Attachment #1.2: 0001-CIFS-fix-mapping-of-SFM_SPACE-and-SFM_PERIOD.patch --]
[-- Type: text/x-diff, Size: 1045 bytes --]
From 0bf80f62d2e7e8cc16dbed7d9e6b9ac2fe40df41 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Jacke?= <bj-3ekOc4rQMZmzQB+pC5nmwQ@public.gmane.org>
Date: Wed, 3 May 2017 23:47:44 +0200
Subject: [PATCH] CIFS: fix mapping of SFM_SPACE and SFM_PERIOD
- trailing space maps to 0xF028
- trailing period maps to 0xF029
Signed-off-by: Bjoern Jacke <bjacke-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
---
fs/cifs/cifs_unicode.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/cifs/cifs_unicode.h b/fs/cifs/cifs_unicode.h
index 3d7298c..7bfb76e 100644
--- a/fs/cifs/cifs_unicode.h
+++ b/fs/cifs/cifs_unicode.h
@@ -64,8 +64,8 @@
#define SFM_LESSTHAN ((__u16) 0xF023)
#define SFM_PIPE ((__u16) 0xF027)
#define SFM_SLASH ((__u16) 0xF026)
-#define SFM_PERIOD ((__u16) 0xF028)
-#define SFM_SPACE ((__u16) 0xF029)
+#define SFM_SPACE ((__u16) 0xF028)
+#define SFM_PERIOD ((__u16) 0xF029)
/*
* Mapping mechanism to use when one of the seven reserved characters is
--
2.7.4
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2017-05-03 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:06 Björn JACKE [this message]
[not found] ` <20170503220632.GA20285-PS7XAnAlDA+VvDNblw4Uiw@public.gmane.org>
2017-05-04 0:41 ` [PATCH] CIFS: fix mapping of SFM_SPACE and SFM_PERIOD Steve French
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=20170503220632.GA20285@SerNet.DE \
--to=bjacke-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.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.