From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] event/octeontx: fix flush callback
Date: Sun, 24 Jun 2018 16:59:36 +0530 [thread overview]
Message-ID: <20180624112934.GA9384@jerin> (raw)
In-Reply-To: <20180617142745.GA27164@jerin>
-----Original Message-----
> Date: Sun, 17 Jun 2018 19:57:46 +0530
> From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> CC: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] event/octeontx: fix flush callback
> User-Agent: Mutt/1.10.0 (2018-05-17)
>
>
> -----Original Message-----
> > Date: Fri, 15 Jun 2018 11:14:06 +0530
> > From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > To: jerin.jacob@caviumnetworks.com
> > Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH] event/octeontx: fix flush callback
> > X-Mailer: git-send-email 2.17.1
> >
> > When event queues are being flushed the getwork operation used to extract
> > events should be a grouped getwork operation to the specific event queue.
> >
> > Fixes: 8384f0e039ea ("event/octeontx: support device stop flush callback")
>
> Cc: stable@dpdk.org
>
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2018-06-24 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 5:44 [PATCH] event/octeontx: fix flush callback Pavan Nikhilesh
2018-06-17 14:27 ` Jerin Jacob
2018-06-24 11:29 ` Jerin Jacob [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=20180624112934.GA9384@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.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 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.