From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alexander Graf <agraf@suse.de>,
Prarit Bhargava <prarit@redhat.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PULL] Module fixes, and a virtio block fix.
Date: Mon, 21 Jan 2013 12:02:47 +1030 [thread overview]
Message-ID: <87fw1vwcao.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CA+55aFwzdcv0LXovZobha=EH=L6DapJt+ODP0nq=TWWAqCxLYQ@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Sun, Jan 20, 2013 at 4:08 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 fixes
>
> Ugh.
>
> You *meant* the "fixes-for-linus" tag, not the "fixes" branch.
>
> Either you mistyped, or you have one of the unfortunate old git
> versions that silently "fixed" the branch name for you to the first
> one it saw.
>
> Either way, please fix for future pull requests...
Ugh indeed.
Due to the delay on git.kernel.org, git request-pull fails. It *looks*
like it succeeds, except the warning, but (as we learned last time I
screwed up), it doesn't put the branchname because it can't know.
So this time I fixed it manually. Badly.
For want of a better solution, I'll now resort to sending pull requests
with the anti-social gitolite URL in it, like so:
The following changes since commit a7f2a366f62319dfebf8d4dfe8b211f631c78457:
ima: fallback to MODULE_SIG_ENFORCE for existing kernel module syscall (2012-12-24 09:35:48 -0500)
are available in the git repository at:
gitolite@ra.kernel.org:/pub/scm/linux/kernel/git/rusty/linux.git tags/fixes-for-linus
for you to fetch changes up to 8f82d479da05bd7df8cca3a5fbc0273f73b601c0:
module: potential deadlock in error path (2013-01-21 11:29:33 +1030)
----------------------------------------------------------------
Various minor fixes, but a slightly more complex one to fix the per-cpu overload
problem introduced recently by kvm id changes.
(Now with an error path fix from Dan, thanks)
----------------------------------------------------------------
Alexander Graf (1):
virtio-blk: Don't free ida when disk is in use
Dan Carpenter (1):
module: potential deadlock in error path
Rusty Russell (2):
module: add new state MODULE_STATE_UNFORMED.
module: put modules in list much earlier.
Sasha Levin (1):
module: prevent warning when finit_module a 0 sized file
drivers/block/virtio_blk.c | 7 +-
include/linux/module.h | 10 +--
kernel/debug/kdb/kdb_main.c | 2 +
kernel/module.c | 156 ++++++++++++++++++++++++++++++-------------
lib/bug.c | 1 +
5 files changed, 124 insertions(+), 52 deletions(-)
next prev parent reply other threads:[~2013-01-21 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 0:08 [PULL] Module fixes, and a virtio block fix Rusty Russell
2013-01-21 0:45 ` Linus Torvalds
2013-01-21 1:32 ` Rusty Russell [this message]
2013-01-21 1:45 ` Linus Torvalds
2013-01-21 2:00 ` Junio C Hamano
2013-01-21 2:14 ` Linus Torvalds
2013-01-21 2:57 ` Rusty Russell
2013-01-21 3:15 ` Linus Torvalds
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=87fw1vwcao.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=agraf@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=sasha.levin@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox