linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dledford@redhat.com
Cc: saeedm@mellanox.com, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, leonro@mellanox.com,
	jgg@mellanox.com
Subject: Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events
Date: Fri, 01 Jun 2018 11:45:58 -0400 (EDT)	[thread overview]
Message-ID: <20180601.114558.569563972122502762.davem@davemloft.net> (raw)
In-Reply-To: <82ddad11b6a77aa07238ff50ae8769360bfb583b.camel@redhat.com>

From: Doug Ledford <dledford@redhat.com>
Date: Fri, 01 Jun 2018 11:08:24 -0400

> On Thu, 2018-05-31 at 15:36 -0400, David Miller wrote:
>> From: Saeed Mahameed <saeedm@mellanox.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/linux.git/log/?h=mlx5-next
>> > 
>> > v1->v2:
>> >   - improve commit message of the FPGA QP error event patch.
>> 
>> Series applied, thanks.
> 
> Hi Dave,
> 
> Although in this case it doesn't really matter and we can work around
> it, this was supposed to be a case of the new methodology that Saeed and
> Jason had worked out with you.  Specifically, when Saeed says in the
> cover letter:
> 
>> 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.
> 
> then it is intended for you to ack the original patch series, not apply
> it, and when acks from both the net and rdma side have been received,
> then we will get a pull request of just that series.

Sorry, I saw your ACK and misinterpreted the situation.

I'll be more careful next time.

  reply	other threads:[~2018-06-01 15:45 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 [this message]
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

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.114558.569563972122502762.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).