From: Long Li <longli@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: RE: [PATCH] net/mana: disable driver by default
Date: Thu, 19 Jan 2023 16:32:12 +0000 [thread overview]
Message-ID: <PH7PR21MB3263C9877B57B769E1579542CEC49@PH7PR21MB3263.namprd21.prod.outlook.com> (raw)
In-Reply-To: <3123906.FA0FI3ke8A@thomas>
> Subject: Re: [PATCH] net/mana: disable driver by default
>
> 19/01/2023 15:49, Ferruh Yigit:
> > On 10/13/2022 12:47 PM, Ferruh Yigit wrote:
> > > Driver is disabled by default because its dependencies are not
> > > upstreamed yet, code is available for development and investigation.
> > >
> > > When all dependencies are upstreamed, driver can be enabled back.
> > >
> > > Fixes: 517ed6e2d590 ("net/mana: add basic driver with build
> > > environment")
> > >
> > > Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
> > > ---
> > > Cc: Long Li <longli@microsoft.com>
> > > Cc: Stephen Hemminger <sthemmin@microsoft.com>
> >
> >
> > Hi Long,
> >
> > I can see mana code is merged to rdma-core, and v44 has it. Are there
> > any more dependencies pending upstream for the driver?
>
> What is the status of the kernel dependency?
The kernel driver is merged in 6.2-rc3. I'm waiting for 6.2 to be released.
>
> > If all dependencies met, can you please send a patch to revert this
> > patch, and to update documentation related to the correct version of
> > dependencies?
>
>
Is it okay to submit the patch now?
Thanks,
Long
next prev parent reply other threads:[~2023-01-19 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 11:47 Ferruh Yigit
2022-10-13 16:30 ` Long Li
2022-10-26 21:53 ` Thomas Monjalon
2022-10-26 22:57 ` Ferruh Yigit
2022-10-27 6:13 ` Thomas Monjalon
2022-10-27 9:04 ` Ferruh Yigit
2023-01-19 14:49 ` Ferruh Yigit
2023-01-19 15:56 ` Thomas Monjalon
2023-01-19 16:32 ` Long Li [this message]
2023-01-19 18:05 ` Thomas Monjalon
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=PH7PR21MB3263C9877B57B769E1579542CEC49@PH7PR21MB3263.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.net \
/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).