Thread (15 messages) 15 messages, 4 authors, 2018-06-02

Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events

From: David Miller <davem@davemloft.net>
Date: 2018-06-02 13:07:41
Also in: linux-rdma

From: Saeed Mahameed <redacted>
Date: Sat, 2 Jun 2018 00:17:37 +0000
On Fri, 2018-06-01 at 17:13 -0700, saeedm@mellanox.com wrote:
quoted
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 !
quoted
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.. 
I really don't like it when others adjust patchwork state on me.
Florian Fainelli did it for a brief time for some of his own patches
and it caused a lot of confusion for me, so I asked him to stop.

Let's just make sure that the Subject line says mlx5-next or whatever
instead of net-next and I'll be mindful in such situations.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help