[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82ddad11b6a77aa07238ff50ae8769360bfb583b.camel@redhat.com>
Date: Fri, 01 Jun 2018 11:08:24 -0400
From: Doug Ledford <dledford@...hat.com>
To: David Miller <davem@...emloft.net>, saeedm@...lanox.com
Cc: netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
leonro@...lanox.com, jgg@...lanox.com
Subject: Re: [PATCH V2 mlx5-next 0/2] Mellanox, mlx5 new device events
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/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.
--
Doug Ledford <dledford@...hat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists