From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Stephen Finucane <stephenfinucane@hotmail.com>
Subject: Re: [dpdk-dev] DPDK patchwork upgrade
Date: Wed, 7 Sep 2016 16:40:08 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9D5C64@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1736050.3Z5tnqk6B6@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, September 07, 2016 8:02 AM
> To: dev@dpdk.org
> Cc: Stephen Finucane
> Subject: [dpdk-dev] DPDK patchwork upgrade
>
> Hi all,
>
> Patchwork is upgraded from a pre-0.9 version to 1.1.1:
> http://dpdk.org/dev/patchwork
>
> This new version brings 2 new columns:
>
> - A/R/T for Acked-by/Reviewed-by/Tested-by counters.
> Unfortunately it does not yet parse the cover letter of a series.
>
> - S/W/F for Success/Warning/Fail counters in tests.
> It will help to integrate the reports of distributed CI from
> http://dpdk.org/ml/archives/test-report/
>
> If you have some concerns or comments about this new version,
> please reply here. I'm sure Stephen Finucane (cc'ed) will be
> interested by our feedbacks.
Good news that patchwork is getting better :)
I am looking at it, and I see two issues:
- There are some patches that have been acked, but I don't see that in patchwork
(e.g. http://dpdk.org/dev/patchwork/patch/15381/)
- Is there any way to see if patches in a patchset have been acked?
Usually, patchsets are acked by replying to the cover letter,
but this is not going to be reflected in Patchwork, correct?
Thanks for the work,
Pablo
> Thanks
next prev parent reply other threads:[~2016-09-07 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:01 Thomas Monjalon
2016-09-07 15:11 ` Stephen Finucane
2016-09-07 16:40 ` De Lara Guarch, Pablo [this message]
2016-09-07 17:01 ` Thomas Monjalon
2016-09-22 6:34 ` Liu, Yong
2016-09-22 8:10 ` Thomas Monjalon
2016-10-10 18:09 ` Stephen Finucane
2016-10-11 8:42 ` Maxim Uvarov
2016-10-11 9:05 ` Stephen Finucane
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=E115CCD9D858EF4F90C690B0DCB4D8973C9D5C64@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=stephenfinucane@hotmail.com \
--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).