netdev - Re: [PATCH net-next 0/7] rxrpc: More fixes and adjustments

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

Message-Id: <20161004.201051.821616397135404483.davem@davemloft.net>
Date:   Tue, 04 Oct 2016 20:10:51 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     dhowells@...hat.com
Cc:     netdev@...r.kernel.org, linux-afs@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/7] rxrpc: More fixes and adjustments

From: David Howells <dhowells@...hat.com>
Date: Tue, 04 Oct 2016 17:01:30 +0100

> What's the procedure for sending more fixes at this point?  Do I send them
> against net-next, since net doesn't contain the things to be fixed yet, or do
> I wait for net to catch up?

I'm sending Linus a pull request later today for the stuff in net-next,
and once he takes that all the trees will be synced up and you can start
sending fixes.

Thanks.