linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "lkml" <linux-kernel@vger.kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Jean Delvare <khali@linux-fr.org>
Cc: Jim Hull <jim.hull@hp.com>
Cc: Mathias Krause <minipli@googlemail.com>
Cc: Rob Landley <rob@landley.net>
Subject: [PULL] modules-next
Date: Wed, 10 Jul 2013 13:25:39 +0930	[thread overview]
Message-ID: <878v1fcblw.fsf@rustcorp.com.au> (raw)

The following changes since commit 06df44ee41442d83be061c5fd1b1de4f5fc6fbbf:

  modpost.c: Add .text.unlikely to TEXT_SECTIONS (2013-05-20 12:08:45 +0930)

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 9eb76d7797b892a1dad4f2efb6f786681306dd13:

  module: cleanup call chain. (2013-07-03 10:15:10 +0930)

----------------------------------------------------------------
Nothing interesting.  Except the most embarrassing bugfix ever.  But let's
ignore that.

Cheers,
Rusty.

----------------------------------------------------------------
Jean Delvare (2):
      There is no /sys/parameters
      ABI: Clarify when /sys/module/MODULENAME is created

Mathias Krause (1):
      module: don't modify argument of module_kallsyms_lookup_name()

Rusty Russell (3):
      modules: don't fail to load on unknown parameters.
      module: do percpu allocation after uniqueness check.  No, really!
      module: cleanup call chain.

 Documentation/ABI/stable/sysfs-module | 10 +++--
 include/linux/moduleparam.h           |  2 +-
 kernel/module.c                       | 77 +++++++++++++++++++----------------
 kernel/params.c                       |  2 +-
 4 files changed, 52 insertions(+), 39 deletions(-)

             reply	other threads:[~2013-07-10  3:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10  3:55 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-08-11  2:32 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-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=878v1fcblw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).