From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Dave Jones <davej@redhat.com>
Cc: Joe Perches <joe@perches.com>
Cc: Michal Nazarewicz <mina86@mina86.com>
Cc: Petr Mladek <pmladek@suse.cz>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>
Subject: [PULL] modules-next
Date: Mon, 11 Aug 2014 12:02:30 +0930 [thread overview]
Message-ID: <87sil3ah8h.fsf@rustcorp.com.au> (raw)
The following changes since commit 15ba2236f3556fc01b9ca91394465152b5ea74b6:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2014-07-21 22:46:01 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/modules-next-for-linus
for you to fetch changes up to 76215b04fd297c008b91ece732ed36e67e0181fa:
arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files (2014-08-07 22:38:55 +0930)
----------------------------------------------------------------
This finally applies the stricter sysfs perms checking we pulled out
before last merge window. A few stragglers are fixed (thanks linux-next!)
Cheers,
Rusty.
----------------------------------------------------------------
Michal Nazarewicz (1):
scripts: modpost: fix compilation warning
Petr Mladek (2):
module: add within_module() function
module: return bool from within_module*()
Rasmus Villemoes (1):
scripts: modpost: Remove numeric suffix pattern matching
Russell King (1):
ARM: avoid ARM binutils leaking ELF local symbols
Rusty Russell (5):
modules: Fix build error in moduleloader.h
sysfs: disallow world-writable files.
drivers/video/fbdev/s3c2410fb.c: don't make debug world-writable.
arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs files
arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files
arch/powerpc/platforms/powernv/opal-dump.c | 4 +--
arch/powerpc/platforms/powernv/opal-elog.c | 4 +--
drivers/video/fbdev/s3c2410fb.c | 2 +-
include/linux/kernel.h | 2 ++
include/linux/module.h | 11 ++++--
include/linux/moduleloader.h | 6 ++--
kernel/module.c | 14 ++++----
scripts/mod/modpost.c | 58 ++++++++----------------------
8 files changed, 40 insertions(+), 61 deletions(-)
next reply other threads:[~2014-08-11 2:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 2:32 Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-01 1:02 [PULL] modules-next Rusty Russell
2016-08-01 1:44 ` Linus Torvalds
2016-08-01 19:11 ` Ben Hutchings
2016-08-02 0:10 ` Rusty Russell
2016-08-04 0:50 ` Rusty Russell
2015-11-08 23:42 Rusty Russell
2015-06-30 2:47 Rusty Russell
2015-02-13 6:43 Rusty Russell
2014-12-19 0:55 Rusty Russell
2014-12-19 5:01 ` Linus Torvalds
2014-12-22 1:21 ` Rusty Russell
2014-09-16 15:48 Rusty Russell
2014-06-11 5:33 Rusty Russell
2014-06-11 10:55 ` Mark Brown
2014-06-12 1:25 ` Rusty Russell
2014-06-12 11:27 ` Mark Brown
2014-06-13 1:03 ` Rusty Russell
2014-06-13 9:24 ` Mark Brown
2014-06-13 10:04 ` Geert Uytterhoeven
2013-07-10 3:55 Rusty Russell
2013-02-19 23:14 Rusty Russell
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=87sil3ah8h.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.