From: Ravi Kerur <rkerur@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/7] Move EAL common function
Date: Thu, 9 Apr 2015 12:45:18 -0700 [thread overview]
Message-ID: <CAFb4SLDx2arVCSungOOoG5UTEnA7M6DT0rSpLv6VmfRUKDMgXw@mail.gmail.com> (raw)
In-Reply-To: <CAFb4SLCbHiLbYm37TgZ+4sa8xe74bxqeWZKYNscHCMuattrquw@mail.gmail.com>
Thomas, Any additional tests i need to do on linux/bsd for v5 series please
let me know.
Thanks,
Ravi
On Tue, Mar 31, 2015 at 11:39 AM, Ravi Kerur <rkerur@gmail.com> wrote:
> I will work on it and send out patches by next week. If you need it
> earlier please let me know.
>
> Thanks,
> Ravi
>
> On Mon, Mar 30, 2015 at 4:24 PM, Thomas Monjalon <
> thomas.monjalon@6wind.com> wrote:
>
>> 2015-03-30 16:15, Ravi Kerur:
>> > On Mon, Mar 30, 2015 at 2:29 PM, Thomas Monjalon <
>> thomas.monjalon@6wind.com> wrote:
>> > > Sorry for not integrating this big refactoring in release 2.0.
>> > > It wasn't easy to merge it during development of some EAL features.
>> > > And it's now too risky to rework it before the release.
>> > > I think this clean-up is needed and should be done at the beginning
>> of 2.1
>> > > cycle. We just need to rebase it and remove the "ifdef BSD/LINUX"
>> which was
>> > > introduced in pci code.
>> > >
>> > > Do you think you'll have time for it?
>> >
>> > Sure, please let me know when it is needed I can work on it.
>>
>> 2.1 cycle is starting in few days.
>> So the sooner is the better.
>>
>> Thanks a lot Ravi
>>
>
>
next prev parent reply other threads:[~2015-04-09 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 17:24 Ravi Kerur
2015-03-30 21:29 ` Thomas Monjalon
2015-03-30 23:15 ` Ravi Kerur
2015-03-30 23:24 ` Thomas Monjalon
2015-03-31 18:39 ` Ravi Kerur
2015-04-09 19:45 ` Ravi Kerur [this message]
2015-01-06 17:26 Ravi Kerur
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=CAFb4SLDx2arVCSungOOoG5UTEnA7M6DT0rSpLv6VmfRUKDMgXw@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).