From: akpm@linux-foundation.org
To: axel.lin@ingics.com, gshark.jeong@gmail.com, mm-commits@vger.kernel.org
Subject: [merged] drivers-video-backlight-lm3639_blc-fix-up-world-writable-sysfs-file.patch removed from -mm tree
Date: Tue, 18 Dec 2012 12:05:30 -0800 [thread overview]
Message-ID: <20121218200530.AAFB782004A@wpzn4.hot.corp.google.com> (raw)
The patch titled
Subject: drivers/video/backlight/lm3639_bl.c: fix up world writable sysfs file
has been removed from the -mm tree. Its filename was
drivers-video-backlight-lm3639_blc-fix-up-world-writable-sysfs-file.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Axel Lin <axel.lin@ingics.com>
Subject: drivers/video/backlight/lm3639_bl.c: fix up world writable sysfs file
We don't need the sysfs file to be world writable or group writable.
This file is write-only, change it to S_IWUSR (0200).
Signed-off-by: Axel Lin <axel.lin@ingics.com>
Acked-by: "G.Shark Jeong" <gshark.jeong@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/video/backlight/lm3639_bl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/video/backlight/lm3639_bl.c~drivers-video-backlight-lm3639_blc-fix-up-world-writable-sysfs-file drivers/video/backlight/lm3639_bl.c
--- a/drivers/video/backlight/lm3639_bl.c~drivers-video-backlight-lm3639_blc-fix-up-world-writable-sysfs-file
+++ a/drivers/video/backlight/lm3639_bl.c
@@ -214,7 +214,7 @@ out_input:
}
-static DEVICE_ATTR(bled_mode, 0666, NULL, lm3639_bled_mode_store);
+static DEVICE_ATTR(bled_mode, S_IWUSR, NULL, lm3639_bled_mode_store);
/* torch */
static void lm3639_torch_brightness_set(struct led_classdev *cdev,
_
Patches currently in -mm which might be from axel.lin@ingics.com are
origin.patch
linux-next.patch
reply other threads:[~2012-12-18 20:05 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=20121218200530.AAFB782004A@wpzn4.hot.corp.google.com \
--to=akpm@linux-foundation.org \
--cc=axel.lin@ingics.com \
--cc=gshark.jeong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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