From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
avijay@marvell.com
Subject: Re: [dpdk-dev] [PATCH] doc: add tested Marvell integrated NIC platforms
Date: Wed, 31 Jul 2019 16:22:39 +0200 [thread overview]
Message-ID: <2892413.ilxcNpkPAj@xps> (raw)
In-Reply-To: <20190731141406.32798-1-jerinj@marvell.com>
31/07/2019 16:14, jerinj@marvell.com:
> From: Jerin Jacob <jerinj@marvell.com>
>
> Add tested Marvell integrated NIC platforms to v19.08 release note.
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> +* ARMv8 SoC combinations from Marvell (with integrated NICs)
> +
> + * SoC:
> +
> + * CN83xx, CN96xx, CNF95xx, CN93xx
> +
> + * OS:
> +
> + * Arch Linux with Marvell OCTEON TX SDK 10.0 package
> + * Build root with Marvell OCTEON TX SDK 10.0 package
There is no space in "Buildroot".
Which version of Buildroot?
> + * Ubuntu 16.04.1 LTS with Marvell OCTEON TX SDK 10.0 package
> + * Ubuntu 16.10 with Marvell OCTEON TX SDK 10.0 package
> + * Ubuntu 18.04.1 LTS with Marvell OCTEON TX SDK 10.0 package
> + * Ubuntu 19.04 with Marvell OCTEON TX SDK 10.0 package
Wouldn't it be simpler to add a separate item, below OS, for SDK?
next prev parent reply other threads:[~2019-07-31 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:14 [dpdk-dev] [PATCH] doc: add tested Marvell integrated NIC platforms jerinj
2019-07-31 14:22 ` Thomas Monjalon [this message]
2019-07-31 15:45 ` [dpdk-dev] [PATCH v2] " jerinj
2019-08-02 13:46 ` Mcnamara, John
2019-08-05 15:41 ` Jerin Jacob Kollanukkaran
-- strict thread matches above, loose matches on Subject: below --
2019-11-27 10:58 [dpdk-dev] [PATCH] " jerinj
2019-11-28 1:07 ` Thomas Monjalon
2020-02-25 17:08 jerinj
2020-02-25 17:25 ` David Marchand
2020-05-22 19:46 jerinj
2020-05-24 22: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=2892413.ilxcNpkPAj@xps \
--to=thomas@monjalon.net \
--cc=avijay@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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.