All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [pull request][net-next 00/15] mlx5 updates 2020-12-01
Date: Wed, 02 Dec 2020 12:15:15 -0800	[thread overview]
Message-ID: <5fde80a4326c45950615918e6e51b5d28d4b9e96.camel@kernel.org> (raw)
In-Reply-To: <20201202112059.0f9f7475@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>

On Wed, 2020-12-02 at 11:20 -0800, Jakub Kicinski wrote:
> On Wed, 02 Dec 2020 11:17:16 -0800 Saeed Mahameed wrote:
> > On Wed, 2020-12-02 at 10:48 -0800, Jakub Kicinski wrote:
> > > On Tue, 1 Dec 2020 14:41:53 -0800 Saeed Mahameed wrote:  
> > > > Please note that the series starts with a merge of mlx5-next
> > > > branch,
> > > > to resolve and avoid dependency with rdma tree.  
> > > 
> > > Why is that not a separate posting prior to this one?  
> > 
> > you mean this ? 
> > https://patchwork.kernel.org/project/linux-rdma/cover/20201120230339.651609-1-saeedm@nvidia.com/
> > 
> > it was posted and we discussed it.
> 
> Yeah but that's not a pull request, I can't pull that.
> 
> > > The patches as posted on the ML fail to build.  
> > 
> > Well, you need to pull the whole thing :/ .. 
> > this is how i used to work with Dave on the mlx5-next branch.
> 
> To be clear - I'm asking you to send a PR for the pre-reqs and then
> send the ethernet patches. So that the pre-reqs are in the tree
> already
> by the time the ethernet patches hit the ML. I thought that's what
> you
> did in the past, but either way it'd make my life easier.

Ok, Done, will submit two separate pull requests.

But to avoid any wait and to create full visibility, is there a way to
let the CI bot understand dependency between two separate pull requests
? or the base-commit of a pull request ?

I would like to send everything in one shot for full visibility.

Thanks,
Saeed.


  reply	other threads:[~2020-12-02 20:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 22:41 [pull request][net-next 00/15] mlx5 updates 2020-12-01 Saeed Mahameed
2020-12-01 22:41 ` [net-next 01/15] net/mlx5e: Free drop RQ in a dedicated function Saeed Mahameed
2020-12-01 22:41 ` [net-next 02/15] net/mlx5e: Allow CQ outside of channel context Saeed Mahameed
2020-12-01 22:41 ` [net-next 03/15] net/mlx5e: Allow RQ " Saeed Mahameed
2020-12-01 22:41 ` [net-next 04/15] net/mlx5e: Allow SQ " Saeed Mahameed
2020-12-01 22:41 ` [net-next 05/15] net/mlx5e: Change skb fifo push/pop API to be used without SQ Saeed Mahameed
2020-12-01 22:41 ` [net-next 06/15] net/mlx5e: Split SW group counters update function Saeed Mahameed
2020-12-01 22:42 ` [net-next 07/15] net/mlx5e: Move MLX5E_RX_ERR_CQE macro Saeed Mahameed
2020-12-01 22:42 ` [net-next 08/15] net/mlx5e: Add TX PTP port object support Saeed Mahameed
2020-12-01 22:42 ` [net-next 09/15] net/mlx5e: Add TX port timestamp support Saeed Mahameed
2020-12-01 22:42 ` [net-next 10/15] net/mlx5e: remove unnecessary memset Saeed Mahameed
2020-12-01 22:42 ` [net-next 11/15] net/mlx5e: Remove duplicated include Saeed Mahameed
2020-12-01 22:42 ` [net-next 12/15] net/mlx5: Arm only EQs with EQEs Saeed Mahameed
2020-12-01 22:42 ` [net-next 13/15] net/mlx5: Fix passing zero to 'PTR_ERR' Saeed Mahameed
2020-12-01 22:42 ` [net-next 14/15] net/mlx5e: Split between RX/TX tunnel FW support indication Saeed Mahameed
2020-12-01 22:42 ` [net-next 15/15] net/mlx5e: Fill mlx5e_create_cq_param in a function Saeed Mahameed
2020-12-02 18:48 ` [pull request][net-next 00/15] mlx5 updates 2020-12-01 Jakub Kicinski
2020-12-02 19:17   ` Saeed Mahameed
2020-12-02 19:20     ` Jakub Kicinski
2020-12-02 20:15       ` Saeed Mahameed [this message]
2020-12-02 20:37         ` Jakub Kicinski

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=5fde80a4326c45950615918e6e51b5d28d4b9e96.camel@kernel.org \
    --to=saeed@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.