linux-kernel - Re: linux-next: time to start cleaning up

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] [day] [month] [year] [list]

Date:	Sat, 14 Jun 2014 01:13:16 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	linux-next list <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: time to start cleaning up

Hi Bjorn,

On Fri, 13 Jun 2014 08:56:26 -0600 Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>
> On Thu, Jun 12, 2014 at 8:06 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
\> >
> > See $subject.  Especially those of you who sent Linus something
> > different to what you have sent me :-(
> 
> Sorry to be dense here, but do you have something in particular in
> mind?  As far as I know, everything I've sent to Linus is in
> linux-next, but if there's something else you'd like me to clean up,
> let me know what it is.

There is nothing for you (in particular) to do.  My comments were
mainly aimed at those who rebased (or otherwise rewrote) the commits in
their branch just before sending it to Linus, but then neglected to
update the branch in linux-next.  I see this as conflicts some of the
time ...

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

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)