DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrzej Ostruszka <amo@semihalf.com>,
	dev@dpdk.org, dpdk-web <web@dpdk.org>
Subject: Re: [dpdk-web] [dpdk-dev] [PATCH v3 0/8] Add Marvell NETA PMD
Date: Wed, 19 Sep 2018 18:39:43 +0100	[thread overview]
Message-ID: <a8c60c99-26a2-c39d-8c5a-0265ad5e5989@intel.com> (raw)
In-Reply-To: <e7d35cb8-574c-0b96-5938-9aed66e96663@semihalf.com>

On 9/19/2018 4:07 PM, Andrzej Ostruszka wrote:
> On 14.09.2018 18:20, Ferruh Yigit wrote:
>> On 8/31/2018 1:59 PM, Andrzej Ostruszka wrote:
>>> This patch series introduces new PMD for Marvell NETA adapters (MVNETA).
>>> See the documentation for more info.
> [...]
>> Hi Andrzej,
>>
>> Patchset is mostly looks good to me, there is no major issue but I have
>> commented on some minor issues.
> 
> Thank you Ferruh for taking time to review it.  I have just pushed out
> new version incorporating your suggestions.
> 
>> Can you also set a web page patch to add new hardware to supported hw list:
>> http://core.dpdk.org/supported/
>> https://git.dpdk.org/tools/dpdk-web/
> 
> Could you tell me what is the procedure for submitting web page patches?
>  Same as for code (sending via e-mail to dev)?

Same process but different mail list: web@dpdk.org

       reply	other threads:[~2018-09-19 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1535718368-15803-1-git-send-email-amo@semihalf.com>
     [not found] ` <1535720386-18775-1-git-send-email-amo@semihalf.com>
     [not found]   ` <c0b0c589-fa08-8543-c2fe-82d71bbd8eb2@intel.com>
     [not found]     ` <e7d35cb8-574c-0b96-5938-9aed66e96663@semihalf.com>
2018-09-19 17:39       ` Ferruh Yigit [this message]
2018-09-21 11:59         ` Andrzej Ostruszka
2018-09-21 13:37           ` Ferruh Yigit

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=a8c60c99-26a2-c39d-8c5a-0265ad5e5989@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amo@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=web@dpdk.org \
    /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).