test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Yash Sharma <ysharma@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Status of Submitted Patch
Date: Wed, 26 Jun 2019 08:25:23 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC527B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <MN2PR18MB335945DD0271A6810312313DA5E70@MN2PR18MB3359.namprd18.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

Hi Yash,

Sorry, currently  we don't have tools like patchwork to monitor patch status.
You can skimpily track your patch through mail list:  https://mails.dpdk.org/archives/dts/ , If the patch get some comments or applied, someone will reply to it.
If you haven't received any response for a long time, you can email me, regularly I work on DTS maintaining every Wednesday.
BTW, I didn't get your patch except https://mails.dpdk.org/archives/dts/2019-June/006377.html



From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yash Sharma
Sent: Friday, June 21, 2019 3:34 PM
To: dts@dpdk.org
Subject: [dts] Status of Submitted Patch

Hi,

I have submitted a patch to dts@dpdk.org<mailto:dts@dpdk.org> using "git send-email" and it's been a week, I haven't received any response.
I am aware that for checking status of dpdk patches there is "http://patchwork.dpdk.org/".
Is there any similar facility for monitoring status of DTS patches as well.

Thanks,
Yash

[-- Attachment #2: Type: text/html, Size: 4207 bytes --]

  reply	other threads:[~2019-06-26  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21  7:34 Yash Sharma
2019-06-26  8:25 ` Tu, Lijuan [this message]
2019-06-26 11:23   ` Yash Sharma

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=8CE3E05A3F976642AAB0F4675D0AD20E0BAC527B@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=ysharma@marvell.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).