linux-kernel - Re: Linux-next changes for module and virtio trees.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Oct 2012 01:12:39 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	<virtualization@...ts.linux-foundation.org>,
	"kvm-devel" <kvm@...r.kernel.org>
Subject: Re: Linux-next changes for module and virtio trees.

Hi Rusty,

On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell <rusty@...tcorp.com.au> wrote:
>
>         Please remove my quilt tree
> http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
> git trees from now on:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
> Branches:
>         modules-next
>         virtio-next

Done.

> For others: beware that these will rebase, usually once after the merge
> window closes (so I can work on a more modern tree), and again just
> before it opens (where I squash in fixup patches).

The first should not be necessary since everything in these trees should
have been merged by Linus during the merge window, so a merge of -rc1 or
later should be a fast forward (though merging with the tag itself may
produce a real merge).  The second can be tricky to pick the right
moment :-)

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped