DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	Jacek Siuda <jck@semihalf.com>,
	Tomasz Duszynski <tdu@semihalf.com>,
	Dmitri Epshtein <dima@marvell.com>,
	Natalie Samsonov <nsamsono@marvell.com>,
	Jianbo Liu <jianbo.liu@arm.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] Documentation build is broken because of missing nics/mrvl
Date: Tue, 3 Apr 2018 18:49:59 +0300	[thread overview]
Message-ID: <3cd6ebbf-c802-d8d1-bc8d-0b1d24a7d154@solarflare.com> (raw)
In-Reply-To: <607d46ec-285e-67cb-5cfa-030f631da5da@intel.com>

On 04/03/2018 06:36 PM, Ferruh Yigit wrote:
> On 4/3/2018 3:35 PM, Andrew Rybchenko wrote:
>> Hi all,
>>
>> documentation build is broken because of Marvell PMD renaming and using of old
>> name in 17.11 release notes.
>> Could someone fix it?
>>
>> /tmp/dpdk-next-net/doc/guides/rel_notes/release_17_11.rst:58: WARNING: unknown
>> document: ../nics/mrvl
>>
>> I guess fixing release notes is the only way.
> I saw it but I am not sure to update previous release notes.

Me too

> And Jerin already send the patch [1]
>
> [1]
> https://dpdk.org/dev/patchwork/patch/36851/

Thanks.

      reply	other threads:[~2018-04-03 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 14:35 Andrew Rybchenko
2018-04-03 15:36 ` Ferruh Yigit
2018-04-03 15:49   ` Andrew Rybchenko [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=3cd6ebbf-c802-d8d1-bc8d-0b1d24a7d154@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=dima@marvell.com \
    --cc=ferruh.yigit@intel.com \
    --cc=jck@semihalf.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@arm.com \
    --cc=john.mcnamara@intel.com \
    --cc=nsamsono@marvell.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=tdu@semihalf.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).