Soft Patch Panel
 help / color / mirror / Atom feed
From: "Choi, Sy Jong" <sy.jong.choi@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: "Rogers, Gerald" <gerald.rogers@intel.com>,
	"srv-apl-arch@lab.ntt.co.jp" <srv-apl-arch@lab.ntt.co.jp>,
	"spp@dpdk.org" <spp@dpdk.org>
Subject: Re: [spp] Question for SPP patch process
Date: Thu, 7 Sep 2017 08:15:03 +0000	[thread overview]
Message-ID: <697F8B1B48670548A5BAB03E8283550F4F7838E1@PGSMSX108.gar.corp.intel.com> (raw)
In-Reply-To: <45c87c87-6143-4285-ed16-80240c1bfc17@lab.ntt.co.jp>

Hi Yasufumi-san,

- Who should be receive SPP's patch submission at least? Is anyone listed in spp/docs/workflow.md? (For DPDK, it is dev@dpdk.org)
For SPP: should be SPP mailing list = spp@dpdk.org

- Is patchwork only used for DPDK and not for other projects, for instance, pktgen or so? I don't just know how patchwork is used in reviewing process.
Pktgen and SPP might not be as strict, but we need to get everyone on the same page. 
http://patchwork.github.io/

- Do you have any idea of updating workflow.md to clear patch submission?
I think if we want to add additional name, we can discuss about this using spp@dpdk.org mailing list.

Regards
Choi, Sy Jong
Platform Application Engineer

-----Original Message-----
From: Yasufumi Ogawa [mailto:ogawa.yasufumi@lab.ntt.co.jp] 
Sent: Thursday, September 7, 2017 3:48 PM
To: Choi, Sy Jong <sy.jong.choi@intel.com>
Cc: Rogers, Gerald <gerald.rogers@intel.com>; srv-apl-arch@lab.ntt.co.jp
Subject: Re: Question for SPP patch process

Hi Sy Jong-san,

Thank you for your mention. I understand I did not know some detains and 
   was against for the patch contribution rule. Your material is so helpful!

I have few quick questions for rules. I'd appreciate if you respond to it.

- Who should be receive SPP's patch submission at least? Is anyone listed in spp/docs/workflow.md? (For DPDK, it is dev@dpdk.org)

- Is patchwork only used for DPDK and not for other projects, for instance, pktgen or so? I don't just know how patchwork is used in reviewing process.

- Do you have any idea of updating workflow.md to clear patch submission?

Regards,
Yasufumi

On 2017/08/23 10:04, Choi, Sy Jong wrote:
> Hi Ogawa-san,
> 
> I manage to find a ppt for submitting patch in dpdk.org, let me share it with you.
> 
> Regards
> Choi, Sy Jong
> Platform Application Engineer
> 
> -----Original Message-----
> From: Yasufumi Ogawa [mailto:ogawa.yasufumi@lab.ntt.co.jp]
> Sent: Friday, August 4, 2017 1:55 PM
> To: Choi, Sy Jong <sy.jong.choi@intel.com>
> Cc: Rogers, Gerald <gerald.rogers@intel.com>; 
> srv-apl-arch@lab.ntt.co.jp
> Subject: Question for SPP patch process
> 
> Hi Sy Jong-san,
> 
> I re-sent patches to you and spp@dpdk.org after Ferruh had advised me for my mistake. I am not sure if I need to do anything next, or wait for your reply. I would like to confirm patch applying process because I am thinking to start working for other patches of our extension for spp_nfv for SR-IOV emulation.
> 
> Regards,
> Yasufumi
> 
> --
> -------------------------------------------------
> Yasufumi Ogawa
> NTT Network Service Systems Labs
> tel: 0422(59)5776  fax: 0422(59)5653
> email: ogawa.yasufumi@lab.ntt.co.jp
> -------------------------------------------------
> 


--
-------------------------------------------------
Yasufumi Ogawa
NTT Network Service Systems Labs
tel: 0422(59)5776  fax: 0422(59)5653
email: ogawa.yasufumi@lab.ntt.co.jp
-------------------------------------------------


       reply	other threads:[~2017-09-07  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fe405293-06cf-3727-ef7e-7c2cdbe6776e@lab.ntt.co.jp>
     [not found] ` <697F8B1B48670548A5BAB03E8283550F4F76CC78@PGSMSX108.gar.corp.intel.com>
     [not found]   ` <45c87c87-6143-4285-ed16-80240c1bfc17@lab.ntt.co.jp>
2017-09-07  8:15     ` Choi, Sy Jong [this message]
2017-09-07  9:37       ` Yasufumi Ogawa

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=697F8B1B48670548A5BAB03E8283550F4F7838E1@PGSMSX108.gar.corp.intel.com \
    --to=sy.jong.choi@intel.com \
    --cc=gerald.rogers@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@dpdk.org \
    --cc=srv-apl-arch@lab.ntt.co.jp \
    /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).