From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Tim McDaniel <timothy.mcdaniel@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] eventdev: clarify usage of forward and release ops
Date: Fri, 15 Sep 2017 18:14:45 +0530 [thread overview]
Message-ID: <20170915124444.GA24508@jerin> (raw)
In-Reply-To: <20170911082900.GA10234@jerin>
-----Original Message-----
> Date: Mon, 11 Sep 2017 13:59:01 +0530
> From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> To: Tim McDaniel <timothy.mcdaniel@intel.com>
> CC: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] eventdev: clarify usage of forward and
> release ops
> User-Agent: Mutt/1.9.0 (2017-09-02)
>
> -----Original Message-----
> > Date: Wed, 6 Sep 2017 10:42:07 -0500
> > From: Tim McDaniel <timothy.mcdaniel@intel.com>
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH v2] eventdev: clarify usage of forward and
> > release ops
> > X-Mailer: git-send-email 2.7.4
> >
> > Update doxygen to make it clear that RTE_EVENT_OP_FORWARD and
> > RTE_EVENT_OP_RELEASE may only be enqueued to the same port that the
>
> s/may/must
>
> > original event was dequeued from.
> >
> > Signed-off-by: Tim McDaniel <timothy.mcdaniel@intel.com>
>
> I could fix the above change on apply.
>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied to dpdk-next-eventdev/master with above change. Thanks.
prev parent reply other threads:[~2017-09-15 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 21:14 [PATCH] eventdev: update doxygen Tim McDaniel
2017-09-06 6:12 ` Jerin Jacob
2017-09-06 15:42 ` [PATCH v2] eventdev: clarify usage of forward and release ops Tim McDaniel
2017-09-11 8:29 ` Jerin Jacob
2017-09-15 12:44 ` 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=20170915124444.GA24508@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=timothy.mcdaniel@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 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.