From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leonro@mellanox.com>,
David Miller <davem@davemloft.net>
Cc: 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 12:48:33 -0400 [thread overview]
Message-ID: <e28570f04bc9aee25b348d6973e1e76bb87e44ef.camel@redhat.com> (raw)
In-Reply-To: <20180601162126.GB2843@mtr-leonro.mtl.com>
[-- Attachment #1: Type: text/plain, Size: 2677 bytes --]
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@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.
>
> 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@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-01 16:48 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 [this message]
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=e28570f04bc9aee25b348d6973e1e76bb87e44ef.camel@redhat.com \
--to=dledford@redhat.com \
--cc=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).