From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: fix octeontx selftest vdev argument
Date: Mon, 11 Jun 2018 15:35:46 +0530 [thread overview]
Message-ID: <20180611100544.GA5431@jerin> (raw)
In-Reply-To: <20180608083323.GA8038@ltp-pvn>
-----Original Message-----
> Date: Fri, 8 Jun 2018 14:03:38 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, stable@dpdk.org,
> dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: fix octeontx selftest vdev argument
> User-Agent: Mutt/1.10.0 (2018-05-17)
>
> On Fri, Jun 08, 2018 at 09:02:27AM +0530, Jerin Jacob wrote:
> > Fixes: 3516327e00fd ("event/octeontx: add selftest to device arguments")
> >
> > Cc: pbhagavatula@caviumnetworks.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Applied to dpdk-next-eventdev/master. Thanks.
>
> > ---
> > doc/guides/eventdevs/octeontx.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/doc/guides/eventdevs/octeontx.rst b/doc/guides/eventdevs/octeontx.rst
> > index 3dcf6afbd..18cfc7a9a 100644
> > --- a/doc/guides/eventdevs/octeontx.rst
> > +++ b/doc/guides/eventdevs/octeontx.rst
> > @@ -96,7 +96,7 @@ The tests are run once the vdev creation is successfully complete.
> >
> > .. code-block:: console
> >
> > - --vdev="event_octeontx,self_test=1"
> > + --vdev="event_octeontx,selftest=1"
> >
> >
> > Enable TIMvf stats
> > --
> > 2.17.1
> >
prev parent reply other threads:[~2018-06-11 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 3:32 Jerin Jacob
2018-06-08 8:33 ` Pavan Nikhilesh
2018-06-11 10:05 ` 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=20180611100544.GA5431@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.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 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).