From: Minfei Huang <mnghuan at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] How to contribute to SPDK
Date: Thu, 09 Feb 2017 14:23:20 +0800 [thread overview]
Message-ID: <D1DBEA71-82C5-4C01-86C1-BEC5F4258BE2@gmail.com> (raw)
In-Reply-To: BLUPR0501MB88434847CEADEFE2B92342CA8770@BLUPR0501MB884.namprd05.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
Hi, Wenhua.
The below URL may help you.
http://www.spdk.io/development/
Thanks
Minfei
> On 26 Jan 2017, at 15:22, Wenhua Liu <liuw(a)vmware.com> wrote:
>
> Hi,
>
> While using SPDK NVMF target, I encountered 2 blocking issues at target side. I have fixed the problems. I'd like to contribute my changes to SPDK, how should I do that?
>
> Thanks,
> -Wenhua
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2017-02-09 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 6:23 Minfei Huang [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-13 16:56 [SPDK] How to contribute to SPDK Walker, Benjamin
2017-02-10 0:57 Wenhua Liu
2017-01-26 14:50 Walker, Benjamin
2017-01-26 7:22 Wenhua Liu
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=D1DBEA71-82C5-4C01-86C1-BEC5F4258BE2@gmail.com \
--to=spdk@lists.01.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).