automatic DPDK test reports
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: sys_stv@intel.com
Cc: test-report@dpdk.org, Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci: explicitly call ioport handlers for uio_pci_generic
Date: Tue, 15 Mar 2016 08:18:57 +0100	[thread overview]
Message-ID: <CALwxeUsXh=W3003R9ROrUCfqxJ174PHBSEXNz39WZngoMn8bZQ@mail.gmail.com> (raw)
In-Reply-To: <2d8c1b$rhddcs@fmsmga001.fm.intel.com>

Hello all,

On Tue, Mar 15, 2016 at 8:05 AM,  <sys_stv@intel.com> wrote:
> Test-Label: Intel Niantic on Fedora
> Test-Status: SUCCESS
>
> Patchwork ID: 11517-11520
> http://www.dpdk.org/dev/patchwork/patch/11520/
> Submitter: David Marchand <david.marchand@6wind.com>
> Date: Tue, 15 Mar 2016 07:29:10 +0100
> DPDK git baseline: 94d8f4bf963a701916b141eed7645f8009aa2054
>
> Check patch:Success
>
> Compilation:
> OS: fedora
> Nic: niantic
> GCC: gcc_x86-64, 4.8.3
> x86_64-native-linuxapp-gcc-combined: compile pass
> i686-native-linuxapp-gcc: compile pass
> x86_64-native-linuxapp-gcc: compile pass
> x86_64-native-linuxapp-clang: compile pass
> x86_64-native-linuxapp-gcc-shared: compile pass
> x86_64-native-linuxapp-gcc-debug: compile pass


Not sure I got a description of what is tested by this tool.

I suppose it applies the 4 patches of the patchset I proposed a bit
earlier on top of the current HEAD.
Does it run checkpatch on each patch ?
Does it check that each patch builds fine individually (I mean in an
incremental way) ?

Any other details ?

Maybe a little description on dpdk.org would help.


Thanks.

-- 
David Marchand

  reply	other threads:[~2016-03-15  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  7:05 sys_stv
2016-03-15  7:18 ` David Marchand [this message]
2016-03-16  2:55   ` Liu, Yong

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='CALwxeUsXh=W3003R9ROrUCfqxJ174PHBSEXNz39WZngoMn8bZQ@mail.gmail.com' \
    --to=david.marchand@6wind.com \
    --cc=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=thomas.monjalon@6wind.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 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).