DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: Lijuan Tu <lijuan.tu@intel.com>, ci@dpdk.org
Subject: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
Date: Thu, 11 Mar 2021 09:52:08 -0500	[thread overview]
Message-ID: <f7tr1kleo9z.fsf@dhcp-25.97.bos.redhat.com> (raw)

Hi Ali,

There was a question today about submitting test reports for patches
that belong to other projects.  Specifically, the DTS project (found at
http://patches.dpdk.org/project/dts/list/)

I believe there is no need to do anything different (because patch ID
should be unique across the patchwork instance, so the test report will
go to the correct patch), but wanted to confirm this is correct.

Thanks,
Aaron


             reply	other threads:[~2021-03-11 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 14:52 Aaron Conole [this message]
2021-03-11 15:55 ` Ali Alnubani
2021-03-15 13:56   ` Ali Alnubani
2021-03-25  8:01     ` Tu, Lijuan
2021-03-25  8:14       ` Thomas Monjalon
2021-03-25  8:17         ` Tu, Lijuan
2021-03-25 16:14       ` Aaron Conole
2021-03-26  1:14         ` Tu, Lijuan
2021-06-07 16:00           ` 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=f7tr1kleo9z.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=lijuan.tu@intel.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).