From: Thomas Monjalon <thomas@monjalon.net>
To: Nikhil Agarwal <nikhil.agarwal@linaro.org>
Cc: stable@dpdk.org, "Hunt, David" <david.hunt@intel.com>,
dev@dpdk.org, nikhil.agarwal@nxp.com, hemant.agrawal@nxp.com,
Danny Zhou <danny.zhou@intel.com>,
Cunming Liang <cunming.liang@intel.com>
Subject: Re: [dpdk-stable] [PATCH 1/4] examples/l3fwd-power: fix non Rx intr supported platform
Date: Mon, 15 Jan 2018 18:43:02 +0100 [thread overview]
Message-ID: <2759355.CTGHcWH8zP@xps> (raw)
In-Reply-To: <d3197cb9-d684-69d9-a89e-fcf9ce39610a@intel.com>
13/12/2017 15:21, Hunt, David:
> On 12/12/2017 10:08 AM, Nikhil Agarwal wrote:
> > This existing code cause the platform to start receiving packet
> > immediately irrespective of interrupts available or not.
> > If the platform does not support Rx interrupt, it shall not start
> > receiving packets immediately. It shall let the timer management work.
> >
> > Fixes: aee3bc79cc34 ("examples/l3fwd-power: enable one-shot Rx interrupt and polling switch")
> > Cc: stable@dpdk.org
> > Cc: Danny Zhou <danny.zhou@intel.com>
> > Cc: Cunming Liang <cunming.liang@intel.com>
> >
> > Signed-off-by: Nikhil Agarwal <nikhil.agarwal@linaro.org>
> > ---
>
> ---snip---
>
> Acked-by: David Hunt <david.hunt@intel.com>
Series applied, thanks
prev parent reply other threads:[~2018-01-15 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:08 [PATCH 1/4] examples/l3fwd-power: fix non Rx intr supported platform Nikhil Agarwal
2017-12-12 10:08 ` [PATCH 2/4] examples/l3fwd-power: fix the timer for any platform freq Nikhil Agarwal
2017-12-13 14:22 ` Hunt, David
2017-12-12 10:08 ` [PATCH 3/4] examples/l3fwd-power: replace desc done with Rx queue count Nikhil Agarwal
2017-12-13 14:22 ` Hunt, David
2017-12-12 10:08 ` [PATCH 4/4] examples/l3fwd-power: disable Lsc interrupts Nikhil Agarwal
2017-12-13 14:23 ` Hunt, David
2017-12-13 14:21 ` [PATCH 1/4] examples/l3fwd-power: fix non Rx intr supported platform Hunt, David
2018-01-15 17:43 ` Thomas Monjalon [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=2759355.CTGHcWH8zP@xps \
--to=thomas@monjalon.net \
--cc=cunming.liang@intel.com \
--cc=danny.zhou@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nikhil.agarwal@linaro.org \
--cc=nikhil.agarwal@nxp.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.