From: Jason Gunthorpe <jgg@nvidia.com>
To: Saeed Mahameed <saeedm@nvidia.com>, Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Leon Romanovsky <leonro@nvidia.com>,
Dave Ertman <david.m.ertman@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [pull request][for-next] mlx5-next auxbus support
Date: Fri, 4 Dec 2020 20:26:42 -0400 [thread overview]
Message-ID: <20201205002642.GA1495499@nvidia.com> (raw)
In-Reply-To: <20201204182952.72263-1-saeedm@nvidia.com>
On Fri, Dec 04, 2020 at 10:29:52AM -0800, Saeed Mahameed wrote:
> Hi Jakub, Jason
>
> This pull request is targeting net-next and rdma-next branches.
>
> This series provides mlx5 support for auxiliary bus devices.
>
> It starts with a merge commit of tag 'auxbus-5.11-rc1' from
> gregkh/driver-core into mlx5-next, then the mlx5 patches that will convert
> mlx5 ulp devices (netdev, rdma, vdpa) to use the proper auxbus
> infrastructure instead of the internal mlx5 device and interface management
> implementation, which Leon is deleting at the end of this patchset.
>
> Link: https://lore.kernel.org/alsa-devel/20201026111849.1035786-1-leon@kernel.org/
>
> Thanks to everyone for the joint effort !
>
> Please pull and let me know if there's any problem.
This all looks good, thanks.
Jakub a few notes on shared branch process here..
In general Linus's advice has been to avoid unnecessary merges so
Saeed/Leon have tended to send PRs to one tree or the other based on
need and that PR might have a "catch up" from the other tree. I guess
this one is special because it makes lots of changes in both trees.
Whoever pulls first means the other cannot refuse the PR, so I usually
prefer to let netdev go first. I have more BW to manage trouble on the
RDMA side..
I saw your other request related to the CI failures due to the wrong
branch basis in the build bot. This means you will need to pull every
update to the mlx5 shared branch, even if it is not immediately
relevant to netdev, or have Saeed include the 'base commit' trailer
and teach the build bots to respect it..
Also, I arrange the RDMA merge window PR to be after netdev (usually
on Thursday) so that Linus sees minor RDMA stuff in the netdev
diffstat, and almost no netdev stuff in the RDMA PR.
Cheers,
Jason
next prev parent reply other threads:[~2020-12-05 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 18:29 [pull request][for-next] mlx5-next auxbus support Saeed Mahameed
2020-12-05 0:26 ` Jason Gunthorpe [this message]
2020-12-05 23:36 ` Jakub Kicinski
2020-12-05 23:35 ` Jakub Kicinski
2020-12-06 0:19 ` Jakub Kicinski
2020-12-06 5:03 ` Leon Romanovsky
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=20201205002642.GA1495499@nvidia.com \
--to=jgg@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.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).