From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, David Howells <dhowells@redhat.com>
Subject: Re: [PULL] More module signing fixes.
Date: Thu, 06 Dec 2012 16:27:02 +1030 [thread overview]
Message-ID: <87r4n3g1u9.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CA+55aFyhuC4hp-T7v8XOeaDf2N_DKThg-NpsShkJakyxLy42ww@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, Dec 4, 2012 at 5:45 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
>
> Nothing there. Forgot to push? Forgot to send me the proper tag/branch name?
How did I manage to get git request-pull to screw that up?
Weird. This time seems to be the right branch: fixes.
Thanks,
Rusty.
The following changes since commit df2fc246c8ee8b6067af1fa55d3bc23107457f61:
Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux (2012-12-04 09:32:12 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git fixes
for you to fetch changes up to f3537f91f9be2ce5fcbaa1aa6d787ad0436daec6:
ASN.1: Fix an indefinite length skip error (2012-12-05 11:27:39 +1030)
----------------------------------------------------------------
David Howells (2):
MODSIGN: Don't use enum-type bitfields in module signature info block
ASN.1: Fix an indefinite length skip error
kernel/module_signing.c | 14 +++++++-------
lib/asn1_decoder.c | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
prev parent reply other threads:[~2012-12-06 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 1:45 Rusty Russell
2012-12-05 18:42 ` Linus Torvalds
2012-12-06 5:57 ` Rusty Russell [this message]
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=87r4n3g1u9.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dhowells@redhat.com \
--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
Powered by JetHome