On Fri, 2018-06-01 at 19:21 +0300, Leon Romanovsky wrote: > On Fri, Jun 01, 2018 at 11:45:58AM -0400, David Miller wrote: > > From: Doug Ledford <dledford@xxxxxxxxxx> > > 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@xxxxxxxxxxxx> > > > > 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. > > Doug, Dave > > I would like to clarify this point, we intend to send pull request to only > one maintainer, who actually needs the accepted patches. > > Let's take the RDMA flow counters series as an example: > https://www.spinics.net/lists/linux-rdma/msg65620.html > > This series includes 12 patches for RDMA and 2 shared code > (mlx5-next). Those two patches, the RDMA side will receive as part > of specific pull request and netdev will get them if some netdev > feature down the road will need mlx5-next branch. > > Of course, it is harmless for both of you to pull, but it looks like > extra work which is not needed for you. Ok, thanks for the clarification Leon. -- Doug Ledford <dledford@xxxxxxxxxx> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
