From: David Miller <davem@davemloft.net>
To: saeedm@dev.mellanox.co.il
Cc: saeedm@mellanox.com, dledford@redhat.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@mellanox.com,
talal@mellanox.com, matanb@mellanox.com
Subject: Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20
Date: Mon, 22 Aug 2016 11:49:01 -0700 (PDT) [thread overview]
Message-ID: <20160822.114901.1630384348955570449.davem@davemloft.net> (raw)
In-Reply-To: <CALzJLG-eucDbJc=eo4HPvqnw-nvoXXAR1vsGPts8WFP3NR5T+Q@mail.gmail.com>
From: Saeed Mahameed <saeedm@dev.mellanox.co.il>
Date: Mon, 22 Aug 2016 20:56:43 +0300
> Technical question though. Do i need to create a new tag for the new
> pull request? I mean, should the tag always point to the "up to" patch
> in the pull request? or can I just use the same tag for the new pull
> request with different "up to" commit ?
Since you're obviously not going to be asking me to pull the same
set of changes, the tag by definition will have to be different.
prev parent reply other threads:[~2016-08-22 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 16:50 [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20 Saeed Mahameed
2016-08-22 16:50 ` [PATCH for-next V2 01/17] net/mlx5: Init/Teardown hca commands via mlx5 ifc Saeed Mahameed
2016-08-22 16:50 ` [PATCH for-next V2 02/17] net/mlx5: Access register and MAD IFC " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 07/17] {net,IB}/mlx5: CQ " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 08/17] {net,IB}/mlx5: MKey/PSV " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 10/17] {net,IB}/mlx5: Modify QP " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 12/17] net/mlx5: Improve driver log messages Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 13/17] net/mlx5: Enable setting minimum inline header mode for VFs Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 14/17] net/mlx5: Update mlx5_ifc.h for vxlan encap/decap Saeed Mahameed
[not found] ` <1471884674-22709-1-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-08-22 16:51 ` [PATCH for-next V2 03/17] net/mlx5: PD and UAR commands via mlx5 ifc Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 04/17] net/mlx5: MCG " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 05/17] net/mlx5: Pages management " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 06/17] net/mlx5: EQ " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 09/17] {net,IB}/mlx5: QP/XRCD " Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 11/17] net/mlx5: Unify and improve command interface Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 15/17] net/mlx5: Introduce alloc_encap and dealloc_encap commands Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 16/17] net/mlx5: Modify RQ bitmask from mlx5 ifc Saeed Mahameed
2016-08-22 16:51 ` [PATCH for-next V2 17/17] net/mlx5: Update struct mlx5_ifc_xrqc_bits Saeed Mahameed
2016-08-22 17:11 ` [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20 David Miller
2016-08-22 17:56 ` Saeed Mahameed
2016-08-22 18:49 ` David Miller [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=20160822.114901.1630384348955570449.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=talal@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).