From: "Jan Mędala" <jan@semihalf.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
Alexander Matushevsky <alex@annapurnalabs.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] ena: update PMD to cooperate with latest ENA firmware
Date: Wed, 29 Jun 2016 13:31:12 +0200 [thread overview]
Message-ID: <CANw_3Zdwxe8DmvBK1hi-LS3GXTOWUGr=DO78TrOrVy5JaeGkVw@mail.gmail.com> (raw)
In-Reply-To: <20160629110139.GC3624@bricha3-MOBL3>
Bruce,
We've got a small minor fixes and we will create V3 version later this week
(targeting Friday).
What's final deadline for 16.07 integration?
Regards,
Jan
2016-06-29 13:01 GMT+02:00 Bruce Richardson <bruce.richardson@intel.com>:
> On Fri, Jun 24, 2016 at 12:52:39PM +0100, Bruce Richardson wrote:
> > On Tue, Jun 21, 2016 at 02:05:57PM +0200, Jan Medala wrote:
> > > As requested, big patch splitted into logical pieces for easier review.
> > > Improved style and fixed icc compiler issues.
> > >
> >
> > Thanks for the patch split. However, many of the patches don't have a
> commit
> > message describing (at a high level), what the goal of that patch is and
> how
> > it goes about implementing the changes to achieve that goal. Can you add
> a
> > paragraph or two of commit message to each patch on the set to help
> anyone
> > looking at the code understand what is happening in each patch.
> >
> > Regards,
> > /Bruce
> >
>
> Any update on this set? Is a V3 coming for 16.07 timeframe?
>
> /Bruce
>
>
next prev parent reply other threads:[~2016-06-29 11:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:54 [dpdk-dev] [PATCH] ena: Update " Jan Medala
2016-06-20 16:16 ` Ferruh Yigit
2016-06-21 12:05 ` [dpdk-dev] [PATCH v2 0/6] ena: update " Jan Medala
2016-06-21 12:05 ` [dpdk-dev] [PATCH v2 1/6] ena: update of ENA communication layer Jan Medala
2016-06-21 12:05 ` [dpdk-dev] [PATCH v2 2/6] ena: add debug area and host information Jan Medala
2016-06-21 12:06 ` [dpdk-dev] [PATCH v2 3/6] ena: disable readless communication regarding to HW revision Jan Medala
2016-06-21 12:06 ` [dpdk-dev] [PATCH v2 4/6] ena: allocate coherent memory in node-aware way Jan Medala
2016-06-21 12:06 ` [dpdk-dev] [PATCH v2 5/6] ena: fix memory management issue Jan Medala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 0/6] ena: update PMD to cooperate with latest ENA firmware Jan Medala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 1/6] ena: update of ENA communication layer Jan Medala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 2/6] ena: add debug area and host information Jan Medala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 3/6] ena: disable readless communication regarding to HW revision Jan Medala
2016-07-04 15:43 ` Bruce Richardson
2016-07-05 10:02 ` Jan Mędala
2016-07-05 15:47 ` Bruce Richardson
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 4/6] ena: allocate coherent memory in node-aware way Jan Medala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 5/6] ena: fix memory management issue Jan Medala
2016-07-04 16:27 ` Bruce Richardson
2016-07-05 16:13 ` Bruce Richardson
2016-07-05 17:03 ` Jan Mędala
2016-07-05 17:03 ` Jan Mędala
2016-06-30 15:04 ` [dpdk-dev] [PATCH v3 6/6] ena: fix for icc compiler Jan Medala
2016-07-05 8:52 ` Ferruh Yigit
2016-07-05 16:19 ` Bruce Richardson
2016-07-05 17:03 ` Jan Mędala
2016-07-05 17:04 ` Jan Mędala
2016-07-05 17:10 ` Jan Mędala
2016-07-06 8:14 ` Bruce Richardson
2016-07-06 8:50 ` Jan Mędala
2016-07-08 13:23 ` Bruce Richardson
2016-07-08 14:07 ` Ferruh Yigit
2016-07-08 13:24 ` [dpdk-dev] [PATCH v3 0/6] ena: update PMD to cooperate with latest ENA firmware Bruce Richardson
2016-06-21 12:06 ` [dpdk-dev] [PATCH v2 6/6] ena: fix for icc compiler Jan Medala
2016-06-24 11:52 ` [dpdk-dev] [PATCH v2 0/6] ena: update PMD to cooperate with latest ENA firmware Bruce Richardson
2016-06-29 11:01 ` Bruce Richardson
2016-06-29 11:31 ` Jan Mędala [this message]
2016-06-29 12:28 ` Bruce Richardson
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='CANw_3Zdwxe8DmvBK1hi-LS3GXTOWUGr=DO78TrOrVy5JaeGkVw@mail.gmail.com' \
--to=jan@semihalf.com \
--cc=alex@annapurnalabs.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).