From: Jan Viktorin <viktorin@rehivetech.com>
To: Santosh Shukla <sshukla@mvista.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Buildroot support for DPDK 2.2.0-rc3
Date: Wed, 9 Dec 2015 16:04:36 +0100 [thread overview]
Message-ID: <20151209160436.06b91fcd@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <CAAyOgsZ4rT3cyf_L0-FD+vS+2vYEVN43zHNhGotcJse3tvAWnQ@mail.gmail.com>
On Wed, 9 Dec 2015 20:17:44 +0530
Santosh Shukla <sshukla@mvista.com> wrote:
> Its encouraging.
>
> Could you pl. post buildroot how-to patch to dpdk-dev mailing list, after
> your work gets accepted in buildroot.
Yes. What exactly do you mean by "how-to patch"?
>
> Thanks
>
> On Wed, Dec 9, 2015 at 8:10 PM, Jan Viktorin <viktorin@rehivetech.com>
> wrote:
>
> > Hello,
> >
> > I've posted a new patch set with DPDK support into the Buildroot project:
> >
> > http://lists.busybox.net/pipermail/buildroot/2015-December/146564.html
> >
> > Patchwork:
> >
> > https://patchwork.ozlabs.org/patch/554673/
> > https://patchwork.ozlabs.org/patch/554674/
> > https://patchwork.ozlabs.org/patch/554675/
> >
> > After I integrate the new DPDK install rules and fix some minor issues,
> > I assume that it will be accepted upstream there. Buildroot is useful
> > at least for cross toolchain generation.
> >
> > Regards
> > Jan
> >
> > --
> > Jan Viktorin E-mail: Viktorin@RehiveTech.com
> > System Architect Web: www.RehiveTech.com
> > RehiveTech
> > Brno, Czech Republic
> >
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
next prev parent reply other threads:[~2015-12-09 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 14:40 Jan Viktorin
2015-12-09 14:47 ` Santosh Shukla
2015-12-09 15:04 ` Jan Viktorin [this message]
2015-12-09 15:14 ` Santosh Shukla
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=20151209160436.06b91fcd@pcviktorin.fit.vutbr.cz \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=sshukla@mvista.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).