From: Leah Tekoa <Leah@Ethernitynet.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Shachar Beiser <Shachar@Ethernitynet.com>,
Barak Perlman <Barak@Ethernitynet.com>,
Leah Tekoa <Leah@Ethernitynet.com>
Subject: Re: [dpdk-dev] Patch not seen in the Patchwork
Date: Mon, 15 Oct 2018 08:10:35 +0000 [thread overview]
Message-ID: <AM6PR04MB4215C855A390E4BD0867EC01AEFD0@AM6PR04MB4215.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM6PR04MB4215CC7D7A8ED03016627005AEE70@AM6PR04MB4215.eurprd04.prod.outlook.com>
Hi,
Can someone please take a look and help me with this?
The patch I want to submit is just a small fix of correcting a typo and replacing 'Y' with 'R' while displaying the RED bytes statistics.
As written in my previous email, I followed the instructions under: https://doc.dpdk.org/guides-18.08/contributing/patches.html but my patch was not added to the Patchwork.
Appreciate your help,
Leah.
-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of Leah Tekoa
Sent: October 9, 2018 10:01 AM
To: dev@dpdk.org
Cc: Shachar Beiser <Shachar@Ethernitynet.com>; Barak Perlman <Barak@Ethernitynet.com>
Subject: [dpdk-dev] Patch not seen in the Patchwork
Hi,
My name is Leah Tekoa and I am working at Ethernity Networks.
I am a new contributor to DPDK.
I am trying to submit code to DPDK.
I followed the instructions under: https://doc.dpdk.org/guides-18.08/contributing/patches.html
* I registered to the DPDK development mailing list.
* I registered to the DPDK Patchwork.
* I also registered to: stable@dpdk.org<mailto:stable@dpdk.org> and users@dpdk.org<mailto:users@dpdk.org>.
* I committed my change and followed the instructions regarding the commit message Subject Line and Body.
* I ran the checkpatches.sh and verified the patch is OK.
* I generated the patch with git-format-patch.
* I sent the patch using git-send-mail and got: ‘Result: OK’.
The problem is that I don’t see my patch in the Patchwork.
Note that I did get an email with my patch, that has the dev@dpdk.org<mailto:dev@dpdk.org> on the TO. Also, an internal colleague got my patch email as well.
Can you advise please?
Thanks,
Leah.
prev parent reply other threads:[~2018-10-15 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:00 Leah Tekoa
2018-10-09 8:23 ` Akhil Goyal
2018-10-09 15:09 ` Stephen Hemminger
2018-10-15 8:10 ` Leah Tekoa [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=AM6PR04MB4215C855A390E4BD0867EC01AEFD0@AM6PR04MB4215.eurprd04.prod.outlook.com \
--to=leah@ethernitynet.com \
--cc=Barak@Ethernitynet.com \
--cc=Shachar@Ethernitynet.com \
--cc=dev@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).