From: r k <rkerur@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Q on consolidating linuxapp/bsdapp in eal
Date: Fri, 21 Nov 2014 10:48:16 -0800 [thread overview]
Message-ID: <CAFb4SLCEu4FcM-jBcDS60xzVHFPzznGiBC5LTcudc9usZBCCzw@mail.gmail.com> (raw)
In-Reply-To: <3860463.eeyc4hhm7y@xps13>
Sure will wait for your patchset. If there is anything other than
cleanup that needs to be looked at please let me know. I can start on
that.
Thanks,
Ravi
On Fri, Nov 21, 2014 at 10:23 AM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 2014-11-21 10:13, r k:
>> Thanks to Thomas for providing some inputs on this.
>>
>> I am looking at consolidating common code in linuxapp/bsdapp in
>> librte_eal. I have started with header files and had some questions
>> related to it.
>
> Sorry, I didn't know you already start working on it.
> I'm going to send a patchset with such cleanup because it's needed to
> integrate some new options (from old pending patches).
>
> Please wait my patchset to see what remains to clean-up.
>
> Thanks
> --
> Thomas
prev parent reply other threads:[~2014-11-21 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:13 r k
2014-11-21 18:23 ` Thomas Monjalon
2014-11-21 18:48 ` r k [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=CAFb4SLCEu4FcM-jBcDS60xzVHFPzznGiBC5LTcudc9usZBCCzw@mail.gmail.com \
--to=rkerur@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).