From: David Miller <davem@davemloft.net>
To: leonro@mellanox.com
Cc: dledford@redhat.com, saeedm@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, jgg@mellanox.com
Subject: Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events
Date: Fri, 01 Jun 2018 13:08:18 -0400 (EDT) [thread overview]
Message-ID: <20180601.130818.1180539221546183992.davem@davemloft.net> (raw)
In-Reply-To: <20180601162126.GB2843@mtr-leonro.mtl.com>
From: Leon Romanovsky <leonro@mellanox.com>
Date: Fri, 1 Jun 2018 19:21:26 +0300
> Of course, it is harmless for both of you to pull, but it looks like
> extra work which is not needed for you.
Just put net-next or rdma-next in the subject line(s) and that will
make it very clear what it expected to happen.
next prev parent reply other threads:[~2018-06-01 17:08 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 [this message]
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
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=20180601.130818.1180539221546183992.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--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).