linux-kernel - Re: linux-next: please clean up the livepatching tree

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.2.00.1608030139230.22028@cbobk.fhfr.pm>
Date:	Wed, 3 Aug 2016 01:41:17 +0200 (CEST)
From:	Jiri Kosina <jikos@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: please clean up the livepatching tree

Hi Stephen

On Wed, 3 Aug 2016, Stephen Rothwell wrote:

> The livepatching tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next)
> today consists of only lots of merges 

This is a part we keep discussing from time to time, and I still don't 
understand why it bothers you so much. The only reason is to keep the 
branch non-rebasing, because it has downstreams. Code-wise, it's always 
equivalent to what end up being merged, but without the actual superfluous 
merge commits.

> (and a patch that is also reverted).

This of course is a good justification to rebase for-next exceptionally; 
so I've just that.

Thanks,

-- 
Jiri Kosina
SUSE Labs