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]
Date:   Thu, 5 May 2022 08:38:12 +0300
From:   Leon Romanovsky <leonro@...dia.com>
To:     Alex Williamson <alex.williamson@...hat.com>
CC:     Jason Gunthorpe <jgg@...dia.com>,
        Yishai Hadas <yishaih@...dia.com>, <saeedm@...dia.com>,
        <kvm@...r.kernel.org>, <netdev@...r.kernel.org>, <kuba@...nel.org>,
        <maorg@...dia.com>, <cohuck@...hat.com>
Subject: Re: [PATCH mlx5-next 0/5] Improve mlx5 live migration driver

On Wed, May 04, 2022 at 04:48:17PM -0600, Alex Williamson wrote:
> On Wed, 4 May 2022 18:33:09 -0300
> Jason Gunthorpe <jgg@...dia.com> wrote:
> 
> > On Wed, May 04, 2022 at 02:19:19PM -0600, Alex Williamson wrote:
> > 
> > > > This may go apparently via your tree as a PR from mlx5-next once you'll 
> > > > be fine with.  
> > > 
> > > As Jason noted, the net/mlx5 changes seem confined to the 2nd patch,
> > > which has no other dependencies in this series.  Is there something
> > > else blocking committing that via the mlx tree and providing a branch
> > > for the remainder to go in through the vfio tree?  Thanks,  
> > 
> > Our process is to not add dead code to our non-rebasing branches until
> > we have an ack on the consumer patches.
> > 
> > So you can get a PR from Leon with everything sorted out including the
> > VFIO bits, or you can get a PR from Leon with just the shared branch,
> > after you say OK.
> 
> As long as Leon wants to wait for some acks in the former case, I'm fine
> with either, but I don't expect to be able to shoot down the premise of
> the series.  You folks are the experts how your device works and there
> are no API changes on the vfio side for me to critique here.  Thanks,

I will prepare PR on Sunday/Monday.

Thanks

> 
> Alex
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ