All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Jason Gunthorpe <jgg@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: Sun, 6 Dec 2020 07:03:51 +0200	[thread overview]
Message-ID: <20201206050351.GA210929@unreal> (raw)
In-Reply-To: <20201205161921.28d5cb7e@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>

On Sat, Dec 05, 2020 at 04:19:21PM -0800, Jakub Kicinski wrote:
> On Sat, 5 Dec 2020 15:35:45 -0800 Jakub Kicinski wrote:
> > On Fri, 4 Dec 2020 10:29:52 -0800 Saeed Mahameed wrote:
> > > 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 !
> >
> > Pulled, thanks! (I'll push out after build finishes so may be an hour)
>
> Or not, looks like you didn't adjust to Greg's changes:

Sorry Jakub, It was my mistake.

I'm fixing, folding the changes and pushing new branch now.
Most likely that Saeed will send new pull request on Monday.

Thanks

      reply	other threads:[~2020-12-06  5:04 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
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 [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=20201206050351.GA210929@unreal \
    --to=leonro@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=david.m.ertman@intel.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kuba@kernel.org \
    --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 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.