From: Rasesh Mody <rasesh.mody@qlogic.com>
To: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Harish Patil <harish.patil@qlogic.com>,
Sony Chacko <sony.chacko@qlogic.com>,
Ameen Rahman <ameen.rahman@qlogic.com>
Subject: [dpdk-dev] QEDE pmd v2 patches
Date: Fri, 18 Mar 2016 01:43:23 +0000 [thread overview]
Message-ID: <2552F74A0BCCBE4DBE2AD218C81B2811086C60B6@avmb3.qlogic.org> (raw)
Hi Thomas, Bruce,
We didn't see automated build email for all the patches that we submitted to dpdk.org. Is this expected?
One of our patch, "[PATCH v2 04/10] qede: Add base driver", doesn't show up on dpdk patchworks site http://dpdk.org/dev/patchwork/project/dpdk/list. Is there any action needed from our side?
We received following messages from dpdk build nonfictions. We did apply the patch-set to the latest dpdk tree then and it was applied cleanly. Please let us know if we need to re-submit the patch-set to take care of it.
------------------------------------------
Test-Label: Intel Niantic on Fedora
Test-Status: apply patch error
Patchwork ID: 11395-11402
http://www.dpdk.org/dev/patchwork/patch/11402/
Submitter: Rasesh Mody <rasesh.mody@qlogic.com>
Date: Thu, 10 Mar 2016 05:45:39 -0800
DPDK git baseline: 94b0ad8e0aa556230183f4c4d06b68bfd145dce3
error: patch failed: MAINTAINERS:352
error: MAINTAINERS: patch does not apply
DPDK STV team
------------------------------------------
Thanks,
-Rasesh
next reply other threads:[~2016-03-18 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 1:43 Rasesh Mody [this message]
2016-03-18 8:01 ` 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=2552F74A0BCCBE4DBE2AD218C81B2811086C60B6@avmb3.qlogic.org \
--to=rasesh.mody@qlogic.com \
--cc=ameen.rahman@qlogic.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=sony.chacko@qlogic.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).