From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>,
Long Li <longli@microsoft.com>
Subject: Re: [PATCH] net/mana: disable driver by default
Date: Thu, 27 Oct 2022 10:04:09 +0100 [thread overview]
Message-ID: <01898749-85a9-8f64-fe3d-962af4634fe7@amd.com> (raw)
In-Reply-To: <13126235.dW097sEU6C@thomas>
On 10/27/2022 7:13 AM, Thomas Monjalon wrote:
> 27/10/2022 00:57, Ferruh Yigit:
>> On 10/26/2022 10:53 PM, Thomas Monjalon wrote:
>>> 13/10/2022 18:30, Long Li:
>>>>> Subject: [PATCH] net/mana: disable driver by default
>>>>>
>>>>> 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>
>>>>
>>>> Acked-by: Long Li <longli@microsoft.com>
>>>
>>> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>>>
>>>
>>
>> Applied to dpdk-next-net/main, thanks.
>
> Looks like we cannot dereference the doc:
> doc/guides/nics/mana.rst:document isn't included in any toctree
>
>
ack
Will fix in next-net, and add mana.rst back to index to remove the warning.
next prev parent reply other threads:[~2022-10-27 9:04 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 [this message]
2023-01-19 14:49 ` Ferruh Yigit
2023-01-19 15:56 ` Thomas Monjalon
2023-01-19 16:32 ` Long Li
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=01898749-85a9-8f64-fe3d-962af4634fe7@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.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).