From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eventdev: optimize Rx adapter event enqueue
Date: Mon, 10 Jun 2019 04:20:18 +0000 [thread overview]
Message-ID: <BYAPR18MB242428EBFD3447FCD7D0BF61C8130@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
> -----Original Message-----
> From: Nikhil Rao <nikhil.rao@intel.com>
> Sent: Tuesday, May 28, 2019 6:35 AM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org; Nikhil Rao <nikhil.rao@intel.com>
> Subject: [PATCH] eventdev: optimize Rx adapter event enqueue
>
> Setup event when the Rx queue is added to the adapter in place of
> generating the event when it is being enqueued to the event device.
>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> ---
> lib/librte_eventdev/rte_event_eth_rx_adapter.c | 39 ++++++++++-----------
> -----
Please rebase this patch and send v2.
Git am error log:
[master] [dpdk-next-eventdev] $ git am -3 /tmp/n/eventdev-optimize-Rx-adapter-event-enqueue
Applying: eventdev: optimize Rx adapter event enqueue
error: sha1 information is lacking or useless (lib/librte_eventdev/rte_event_eth_rx_adapter.c).
error: could not build fake ancestor
Patch failed at 0001 eventdev: optimize Rx adapter event enqueue
hint: Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
next reply other threads:[~2019-06-10 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 4:20 Jerin Jacob Kollanukkaran [this message]
2019-06-14 5:02 ` Rao, Nikhil
-- strict thread matches above, loose matches on Subject: below --
2019-06-16 8:39 Jerin Jacob Kollanukkaran
2019-06-16 9:22 ` Jerin Jacob Kollanukkaran
2019-05-28 1:05 Nikhil Rao
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=BYAPR18MB242428EBFD3447FCD7D0BF61C8130@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@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).