From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: dledford@redhat.com, jgg@mellanox.com, leonro@mellanox.com,
ogerlitz@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [pull request][for-next 00/15] Mellanox, mlx5 core and netdev updates 2018-05-17
Date: Fri, 18 May 2018 13:03:51 -0400 (EDT) [thread overview]
Message-ID: <20180518.130351.456975805564832525.davem@davemloft.net> (raw)
In-Reply-To: <20180518012258.26968-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Thu, 17 May 2018 18:22:43 -0700
> Below you can find two pull requests,
>
> 1. mlx5 core updates to be shared for both netdev and RDMA, (patches 1..9)
> which is based on the last mlx5-next pull request
>
> The following changes since commit a8408f4e6db775e245f20edf12b13fd58cc03a1c:
>
> net/mlx5: fix spelling mistake: "modfiy" -> "modify" (2018-05-04 12:11:51 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git tags/mlx5-updates-2018-05-17
>
> for you to fetch changes up to 10ff5359f883412728ba816046ee3a696625ca02:
>
> net/mlx5e: Explicitly set source e-switch in offloaded TC rules (2018-05-17 14:17:35 -0700)
>
> 2. mlx5e netdev updates only for net-next branch (patches 10..15) based on net-next
> and the above pull request.
>
> The following changes since commit 538e2de104cfb4ef1acb35af42427bff42adbe4d:
>
> Merge branch 'net-Allow-more-drivers-with-COMPILE_TEST' (2018-05-17 17:11:07 -0400)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5e-updates-2018-05-17
>
> for you to fetch changes up to a228060a7c9ab88597eeac131e4578595d5d46ae:
>
> net/mlx5e: Add HW vport counters to representor ethtool stats (2018-05-17 17:48:54 -0700)
>
> Dave, for your convenience you can either pull 1. and then 2. or pull 2.
> directly.
Looks good.
I pulled 1 then I pulled 2. That seemed to work well. Particularly
it allowed me to capture the two different merge commit messages one
by one.
Is this basically how you want to handle things moving forward?
Thanks.
next prev parent reply other threads:[~2018-05-18 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 1:22 [pull request][for-next 00/15] Mellanox, mlx5 core and netdev updates 2018-05-17 Saeed Mahameed
2018-05-18 1:22 ` [for-next 01/15] net/mlx5: Vport, Use 'kvfree()' for memory allocated by 'kvzalloc()' Saeed Mahameed
2018-05-18 1:22 ` [for-next 02/15] net/mlx5: Eswitch, " Saeed Mahameed
2018-05-18 1:22 ` [for-next 03/15] IB/mlx5: " Saeed Mahameed
2018-05-18 1:22 ` [for-next 04/15] net/mlx5: Add merged e-switch cap Saeed Mahameed
2018-05-18 1:22 ` [for-next 05/15] net/mlx5: Properly handle a vport destination when setting FTE Saeed Mahameed
2018-05-18 1:22 ` [for-next 06/15] net/mlx5: Add destination e-switch owner Saeed Mahameed
2018-05-18 1:22 ` [for-next 07/15] net/mlx5e: Explicitly set destination e-switch in FDB rules Saeed Mahameed
2018-05-18 1:22 ` [for-next 08/15] net/mlx5: Add source e-switch owner Saeed Mahameed
2018-05-18 1:22 ` [for-next 09/15] net/mlx5e: Explicitly set source e-switch in offloaded TC rules Saeed Mahameed
2018-05-18 1:22 ` [for-next 10/15] net/mlx5e: Offload TC eswitch rules for VFs belonging to different PFs Saeed Mahameed
2018-05-18 1:22 ` [for-next 11/15] net/mlx5e: Add ingress/egress indication for offloaded TC flows Saeed Mahameed
2018-05-18 1:22 ` [for-next 12/15] net/mlx5e: Prepare for shared table to keep TC eswitch flows Saeed Mahameed
2018-05-18 1:22 ` [for-next 13/15] net/mlx5e: Use shared table for offloaded " Saeed Mahameed
2018-05-18 1:22 ` [for-next 14/15] net/mlx5e: Ignore attempts to offload multiple times a TC flow Saeed Mahameed
2018-05-18 1:22 ` [for-next 15/15] net/mlx5e: Add HW vport counters to representor ethtool stats Saeed Mahameed
2018-05-18 17:03 ` David Miller [this message]
2018-05-18 17:21 ` [pull request][for-next 00/15] Mellanox, mlx5 core and netdev updates 2018-05-17 Jason Gunthorpe
2018-05-18 20:36 ` Saeed Mahameed
2018-05-18 20:33 ` Saeed Mahameed
2018-05-22 18:48 ` Doug Ledford
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=20180518.130351.456975805564832525.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=ogerlitz@mellanox.com \
--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