Message ID | 20201201224208.73295-1-saeedm@nvidia.com (mailing list archive) |
---|---|
State | Changes Requested |
Delegated to: | Netdev Maintainers |
Headers | show |
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? The patches as posted on the ML fail to build.
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. > > 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.
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.
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.
On Wed, 02 Dec 2020 12:15:15 -0800 Saeed Mahameed wrote: > On Wed, 2020-12-02 at 11:20 -0800, Jakub Kicinski wrote: > > 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 ? Possibly it's just a python script (available on GH). Although we don't allow people to queue up multiple series which are co-dependent, I'm not sure if using PRs changes that much. There still needs to be a reasonable rate control on number of patches for example. > I would like to send everything in one shot for full visibility. Hm, not sure what you mean by visibility.