From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: jgg@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@mellanox.com
Subject: Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events
Date: Sat, 02 Jun 2018 09:07:39 -0400 (EDT) [thread overview]
Message-ID: <20180602.090739.109800509954239583.davem@davemloft.net> (raw)
In-Reply-To: <a6385f91ca1611184391b1949f26f531ae812911.camel@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Sat, 2 Jun 2018 00:17:37 +0000
> On Fri, 2018-06-01 at 17:13 -0700, saeedm@mellanox.com wrote:
>> 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..
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.
prev parent reply other threads:[~2018-06-02 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:59 [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events Saeed Mahameed
2018-05-30 17:59 ` [PATCH V2 mlx5-next 1/2] net/mlx5: Add temperature warning event to log Saeed Mahameed
2018-05-30 17:59 ` [PATCH V2 mlx5-next 2/2] net/mlx5: Add FPGA QP error event Saeed Mahameed
2018-05-31 18:08 ` [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events Doug Ledford
2018-05-31 19:36 ` David Miller
2018-06-01 15:08 ` Doug Ledford
2018-06-01 15:45 ` David Miller
2018-06-01 16:21 ` Leon Romanovsky
2018-06-01 16:48 ` Doug Ledford
2018-06-01 17:08 ` David Miller
2018-06-01 19:30 ` Leon Romanovsky
2018-06-01 16:49 ` Doug Ledford
2018-06-02 0:13 ` Saeed Mahameed
2018-06-02 0:17 ` Saeed Mahameed
2018-06-02 13:07 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180602.090739.109800509954239583.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).