From: Doug Ledford <dledford@redhat.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: David Miller <davem@davemloft.net>,
saeedm@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@mellanox.com
Subject: Re: [pull request][for-next V3 00/11] Mellanox, mlx5 E-Switch updates 2017-12-19
Date: Fri, 05 Jan 2018 14:33:52 -0500 [thread overview]
Message-ID: <1515180832.3403.34.camel@redhat.com> (raw)
In-Reply-To: <20180105192656.GB11348@ziepe.ca>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, 2018-01-05 at 12:26 -0700, Jason Gunthorpe wrote:
> On Fri, Jan 05, 2018 at 02:07:34PM -0500, Doug Ledford wrote:
>
> > > > V2->V3:
> > > > - Fixed compilation warning, reported by Dave.
> > > >
> > > > Please pull and let me know if there's any problem.
> > >
> > > Looks good, pulled, thank you.
> >
> > Hi Jason,
> >
> > Unless I missed something, you haven't pulled this for for-next,
> > correct?
>
> I was told there are no patches for RDMA that depend on this for this
> cycle, so RDMA does not need it.
Works For Me, thanks.
--
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 --]
prev parent reply other threads:[~2018-01-05 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 23:23 [pull request][for-next V3 00/11] Mellanox, mlx5 E-Switch updates 2017-12-19 Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 02/11] net/mlx5: E-Switch, Refactor load/unload of representors Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 04/11] net/mlx5: E-Switch, Move mlx5e only logic outside E-Switch Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 05/11] net/mlx5: E-Switch, Create a dedicated send to vport rule deletion function Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 06/11] net/mlx5e: Move ethernet representors data into separate struct Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 07/11] net/mlx5: E-Switch, Create generic header struct to be used by representors Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 08/11] net/mlx5e: E-Switch, Move send-to-vport rule struct to en_rep Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 09/11] net/mlx5e: E-Switch, Use the name of static array instead of its address Saeed Mahameed
[not found] ` <20171228232314.13678-1-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-12-28 23:23 ` [for-next V3 01/11] net/mlx5: E-Switch, Refactor vport representors initialization Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 03/11] net/mlx5: E-Switch, Simplify representor load/unload callback API Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 10/11] net/mlx5: Fix ingress/egress naming mistake Saeed Mahameed
2017-12-28 23:23 ` [for-next V3 11/11] net/mlx5: Separate ingress/egress namespaces for each vport Saeed Mahameed
2017-12-29 0:46 ` [pull request][for-next V3 00/11] Mellanox, mlx5 E-Switch updates 2017-12-19 David Miller
[not found] ` <20171228.194616.2274862427545657993.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-01-05 19:07 ` Doug Ledford
[not found] ` <1515179254.3403.32.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-05 19:26 ` Jason Gunthorpe
2018-01-05 19:33 ` Doug Ledford [this message]
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=1515180832.3403.34.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).