DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Alejandro.Lucero <alejandro.lucero@netronome.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] Support for Netronome´s NFP-6xxx card
Date: Wed, 14 Oct 2015 17:16:35 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202382373@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1444142937-29789-1-git-send-email-alejandro.lucero@netronome.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alejandro.Lucero
> Sent: Tuesday, October 6, 2015 3:49 PM
> To: dev@dpdk.org
> Subject: [PATCH v2 0/4] Support for Netronome´s NFP-6xxx card
> 
> From: "Alejandro.Lucero" <alejandro.lucero@netronome.com>
> 
> This patchset adds a new PMD for Netronome´s NFP-6xxx card along with a
> new UIO driver, documentation and minor changes to configuration scrips.

Hi Alejandro,

Patch 1/4 doesn't build cleanly without patch 2/4:


    == Build lib/librte_eal/linuxapp/nfp_uio
    make[7]: /home/johnmc/dpdk_netronome/lib/librte_eal/linuxapp/nfp_uio/Makefile: 
             No such file or directory
    make[7]: *** No rule to make target
             `/tmp/dpdk_netronome/lib/librte_eal/linuxapp/nfp_uio/Makefile'.
             Stop.
    make[6]: *** [nfp_uio] Error 2
    make[5]: *** [linuxapp] Error 2
    make[4]: *** [librte_eal] Error 2
    make[3]: *** [lib] Error 2
    make[2]: *** [all] Error 2
    make[1]: *** [x86_64-native-linuxapp-gcc_install] Error 2
    make: *** [install] Error 2


Patch 3/4 has a whitespace warning in the patch:

    $ pwclient git-am 7472

    Applying patch #7472 using 'git am'
    Description: [dpdk-dev,v2,3/4] This patch adds documentation about Netronome´s NFP nic
    Applying: This patch adds documentation about Netronome´s NFP nic
    /home/johnmc/dpdk_netronome/.git/rebase-apply/patch:291: new blank line at EOF.
    +
    warning: 1 line adds whitespace errors.


The commit messages don't follow the usual DPDK standard which is more or less the same as the Linux kernel format. The subject line should be lowercase, around 60 characters, and contain the component that is being modified. So Patch 1/4 should have a commit message like:

    nfp: add a pmd driver for netronome nfp pci cards

    This patch adds a PMD driver for Netronome NFP PCI cards.
    Or something more informative if necessary.

    Signed-off-by: etc

Do a git log on some of the other components and copy the ones that look right. :-)

John





      parent reply	other threads:[~2015-10-14 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 14:48 [PATCH v2 0/4] Support for Netronome´s " Alejandro.Lucero
2015-10-06 14:48 ` [dpdk-dev] [PATCH v2 1/4] This patch adds a PMD driver for Netronome NFP PCI cards Alejandro.Lucero
2015-10-06 14:48 ` [dpdk-dev] [PATCH v2 2/4] This patch adds a new UIO " Alejandro.Lucero
2015-10-06 14:48 ` [dpdk-dev] [PATCH v2 3/4] This patch adds documentation about Netronome´s NFP nic Alejandro.Lucero
2015-10-06 14:48 ` [dpdk-dev] [PATCH v2 4/4] Modifying configuration scripts for Netronome's nfp_uio driver Alejandro.Lucero
2015-10-14 17:16 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE202382373@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=dev@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).