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: <a6385f91ca1611184391b1949f26f531ae812911.camel@mellanox.com>
Date:   Sat, 2 Jun 2018 00:17:37 +0000
From:   Saeed Mahameed <saeedm@...lanox.com>
To:     "davem@...emloft.net" <davem@...emloft.net>
CC:     Jason Gunthorpe <jgg@...lanox.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        Leon Romanovsky <leonro@...lanox.com>
Subject: Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events

On Fri, 2018-06-01 at 17:13 -0700, saeedm@...lanox.com wrote:
> On Thu, 2018-05-31 at 15:36 -0400, David Miller wrote:
> > From: Saeed Mahameed <saeedm@...lanox.com>
> > Date: Wed, 30 May 2018 10:59:48 -0700
> > 
> > > The following series is for mlx5-next tree [1], it adds the
> > > support
> > > of two
> > > new device events, from Ilan Tayari:
> > > 
> > > 1. High temperature warnings.
> > > 2. FPGA QP error event.
> > > 
> > > In case of no objection this series will be applied to mlx5-next
> > > tree
> > > and will be sent later as a pull request to both rdma and net
> > > trees.
> > > 
> > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linu
> > > x.
> > > git/log/?h=mlx5-next
> > > 
> > > v1->v2:
> > >   - improve commit message of the FPGA QP error event patch.
> > 
> > Series applied, thanks.
> 
> Hey Dave, this series was meant to go to mlx5-next tree as stated in
> the cover letter and patches titles "[PATCH V2 mlx5-next 0/2]".
> 
> It is ok you applied those patches to net-next this time, but for
> next
> time I would like to apply them myself to mlx5-next and send a clean
> pull request later to both rdma and net trees.
> 

Sorry please ignore, I just saw that this was sorted out .. :).
Thanks A lot !

> Is there a way for me to mark them as delegated in patchwork ?
> I see that i have "update Properties" option in patchwork but i don't
> know how to use it or whether I am allowed to do anything with it.
> 

It would be great if we can mark such patches in patchwork though.. 

> Thanks,
> Saeed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ