From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>,
Michal Schmidt <mschmidt@redhat.com>
Subject: Re: [PULL] module and param
Date: Wed, 26 Oct 2011 13:13:58 +1030 [thread overview]
Message-ID: <878vo8pj4h.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CA+55aFyU=GxX+=b=Q2OP3BJNQuth7GWuAv5Zd63n209EJ0VOyw@mail.gmail.com>
On Tue, 25 Oct 2011 09:33:16 +0200, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> [ Cut-and-paste reply: mentally just "sed s/9p/module/g" ]
>
> So for the merge window, I *really* want the development trees I pull
> from explicitly verified some way.
>
> Putting a signed tag on there somewhere that actually signs the top
> commit *and* mentions the repository and branch it is on (ie github)
> is not wonderfully convenient, but it's at least relatively
> straightforward (do I have a gpg key I can trust?).
I'm not sure if this paranoia is disproportionate or overdue. Hope I
did it right (D1ADB8F1, signed by some other OzLabs folks).
Personally I would have thought that asking people to patch a gpg
fingerprint into MAINTAINERS is more kernely than web of trust. I'll
notice if someone else tries to patch their own in there.
Cheers,
Rusty.
To git@github.com:rustyrussell/linux.git
+ 694136c...b1e4d20 master -> master (forced update)
* [new tag] rusty@rustcorp.com.au-v3.1-2-gb1e4d20 -> rusty@rustcorp.com.au-v3.1-2-gb1e4d20
The following changes since commit c3b92c8787367a8bb53d57d9789b558f1295cc96:
Linux 3.1 (2011-10-24 09:10:05 +0200)
are available in the git repository at:
git://github.com/rustyrussell/linux.git master
Jiri Kosina (1):
kmod: prevent kmod_loop_msg overflow in __request_module()
Michal Schmidt (1):
params: make dashes and underscores in parameter names truly equal
include/linux/moduleparam.h | 20 ++++++++++++++++++++
init/main.c | 4 ++--
kernel/kmod.c | 4 +++-
kernel/params.c | 21 ++++++++++++++-------
4 files changed, 39 insertions(+), 10 deletions(-)
next prev parent reply other threads:[~2011-10-26 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 3:43 [PULL] module and param Rusty Russell
2011-10-25 7:33 ` Linus Torvalds
2011-10-26 2:43 ` Rusty Russell [this message]
2011-10-26 12:45 ` Linus Torvalds
2011-10-27 0:45 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2012-03-26 2:34 Rusty Russell
2012-01-12 23:13 Rusty Russell
2011-01-24 4:07 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=878vo8pj4h.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--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.