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  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:   Wed, 29 Apr 2020 12:27:20 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     kgraul@...ux.ibm.com
Cc:     netdev@...r.kernel.org, linux-s390@...r.kernel.org,
        heiko.carstens@...ibm.com, raspl@...ux.ibm.com,
        ubraun@...ux.ibm.com
Subject: Re: [PATCH net-next 00/13] net/smc: preparations for SMC-R link
 failover

From: Karsten Graul <kgraul@...ux.ibm.com>
Date: Wed, 29 Apr 2020 17:10:36 +0200

> This patch series prepares the SMC code for the implementation of SMC-R link 
> failover capabilities which are still missing to reach full compliance with 
> RFC 7609.
> The code changes are separated into 65 patches which together form the new
> functionality. I tried to create meaningful patches which allow to follow the 
> implementation.

Series applied.

> Question: how to handle the remaining 52 patches? All of them are needed for 
> link failover to work and should make it into the same merge window. 
> Can I send them all together?

No.

You must break these changes up into significantly smaller sized,
logical, group of changes.  That's part of your responsibility when
submitting changes, keeping the patch series small and reviewable.

Powered by blists - more mailing lists