From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: test-report@dpdk.org
Subject: Re: [dpdk-test-report] [PatchWork]|ERROR| pw15557-15570 eal/soc: introduce very essential SoC infra definitions
Date: Fri, 02 Sep 2016 11:44:51 +0200 [thread overview]
Message-ID: <11703916.hFsHSV51kG@xps13> (raw)
In-Reply-To: <DB5PR0401MB2054400803165845165C02DE90E50@DB5PR0401MB2054.eurprd04.prod.outlook.com>
2016-09-02 09:28, Shreyansh Jain:
> These patches are failing because these are *over* the rte_driver/device patchset and not direct master. I am not sure how to convey to the test system this.
> Or, is there another way to submit patches which are based over some other patch set? Or maybe I just have to ignore this.
>
> Any comments?
You can ignore these errors.
We can think about a standard way to specify a dependency, but we
need the series support in patchwork (coming).
prev parent reply other threads:[~2016-09-02 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:17 sys_stv
2016-09-02 9:28 ` Shreyansh Jain
2016-09-02 9:44 ` Thomas Monjalon [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=11703916.hFsHSV51kG@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=shreyansh.jain@nxp.com \
--cc=test-report@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).