The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] modules updates for 4.10
Date: Wed, 14 Dec 2016 18:50:41 -0800	[thread overview]
Message-ID: <20161215025040.ofyktfgkdn4c4bvs@jeyu> (raw)

Linus,

Please pull below to receive modules updates for the 4.10 merge window.
This development cycle has been pretty quiet, mostly code cleanups, small
bugfixes. Summary and details in the tag.

Thanks,

Jessica
---

The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6:

  Linux 4.9-rc5 (2016-11-13 10:32:32 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git tags/modules-for-v4.10

for you to fetch changes up to 4d217a5adccf5e806790c37c61cc374a08bd7381:

  module: fix DEBUG_SET_MODULE_RONX typo (2016-11-28 11:37:57 -0800)

----------------------------------------------------------------
Modules updates for v4.10

Summary of modules changes for the 4.10 merge window:

* The rodata= cmdline parameter has been extended to additionally
  apply to module mappings

* Fix a hard to hit race between module loader error/clean up
  handling and ftrace registration

* Some code cleanups, notably panic.c and modules code use a
  unified taint_flags table now. This is much cleaner than
  duplicating the taint flag code in modules.c

Signed-off-by: Jessica Yu <jeyu@redhat.com>

----------------------------------------------------------------
AKASHI Takahiro (1):
      module: extend 'rodata=off' boot cmdline parameter to module mappings

Aaron Tomlin (2):
      module: Ensure a module's state is set accordingly during module coming cleanup code
      module: When modifying a module's text ignore modules which are going away too

Anson Jacob (1):
      module: remove trailing whitespace

Arnd Bergmann (1):
      module: fix DEBUG_SET_MODULE_RONX typo

Heinrich Schuchardt (1):
      modpost: free allocated memory

Miroslav Benes (1):
      module: Fix a comment above strong_try_module_get()

Petr Mladek (1):
      taint/module: Clean up global and module taint flags handling

 include/linux/init.h   |  3 +++
 include/linux/kernel.h |  9 +++++++
 include/linux/module.h |  4 +--
 init/main.c            |  7 +++--
 kernel/module.c        | 69 +++++++++++++++++++++++++++++++-------------------
 kernel/panic.c         | 53 ++++++++++++++++++--------------------
 scripts/mod/modpost.c  |  2 ++
 7 files changed, 89 insertions(+), 58 deletions(-)

                 reply	other threads:[~2016-12-15  2:50 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=20161215025040.ofyktfgkdn4c4bvs@jeyu \
    --to=jeyu@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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