DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vadim Suraev <vadim.suraev@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Userland IP stack for DPDK
Date: Thu, 18 Sep 2014 15:18:20 +0300	[thread overview]
Message-ID: <CAJ0CJ8k_=dRO02e44vd9cygbe6MNvAzT5QnWbFexq84Xb_uZww@mail.gmail.com> (raw)
In-Reply-To: <20140918121658.GC20389@hmsreliant.think-freely.org>

I'll add it. Thanks
On Sep 18, 2014 3:17 PM, "Neil Horman" <nhorman@tuxdriver.com> wrote:

> On Thu, Sep 18, 2014 at 07:13:43AM +0300, Vadim Suraev wrote:
> > Hi,
> > I've published the source code of Linux kernel IP stack ported to user
> space
> > and integrated with DPDK (1.6 currently).
> > I includes also some example applications & test scripts as well as
> > documentation
> > about what & how is done and how to use & adapt it.
> > The source:
> > git@github.com:vadimsu/ipaugenblick.git
> > <
> https://mail.google.com/mail/u/0/git@github.com:vadimsu/ipaugenblick.git>
> > two branches - master & muticore
> > Documentation:
> > - README at the root of the project
> > ipaugenblick.net
> > Please feel free to ask questions you may have
> > Regards,
> >  Vadim.
> >
>
> You copied these files from the Linux Kernel sources, but failed to copy
> the
> GPLv2 license file.  IANAL, but I expect you'll want to include that so as
> to be
> clear about how that code is licensed (copyright isn't included in specific
> kernel files), as well as including a license for your independently
> written
> code (assuming you would like it to be different than GPL v2)
> Neil
>
>

      reply	other threads:[~2014-09-18 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  4:13 Vadim Suraev
2014-09-18  5:44 ` Matthew Hall
2014-09-18 12:16 ` Neil Horman
2014-09-18 12:18   ` Vadim Suraev [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='CAJ0CJ8k_=dRO02e44vd9cygbe6MNvAzT5QnWbFexq84Xb_uZww@mail.gmail.com' \
    --to=vadim.suraev@gmail.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).