DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] event/octeontx2: fix device name in device info
Date: Wed, 15 Jan 2020 17:03:36 +0530	[thread overview]
Message-ID: <CALBAE1NRcwBticxP8g5RPkMo5unSp0QSRzdQZd2hKRtu8wqNnA@mail.gmail.com> (raw)
In-Reply-To: <20200106074318.2670-1-pbhagavatula@marvell.com>

On Mon, Jan 6, 2020 at 1:13 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix imcorrect device name being used in device info.
>
> Fixes: bebc3dbcf4a6 ("event/octeontx2: add device capabilities function")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>


Applied to dpdk-next-eventdev/master. Thanks.



> ---
>  drivers/event/octeontx2/otx2_evdev.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/event/octeontx2/otx2_evdev.h b/drivers/event/octeontx2/otx2_evdev.h
> index 231a12a52..ef523dc9d 100644
> --- a/drivers/event/octeontx2/otx2_evdev.h
> +++ b/drivers/event/octeontx2/otx2_evdev.h
> @@ -16,7 +16,7 @@
>  #include "otx2_mempool.h"
>  #include "otx2_tim_evdev.h"
>
> -#define EVENTDEV_NAME_OCTEONTX2_PMD otx2_eventdev
> +#define EVENTDEV_NAME_OCTEONTX2_PMD event_octeontx2
>
>  #define sso_func_trace otx2_sso_dbg
>
> --
> 2.17.1
>

      reply	other threads:[~2020-01-15 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  7:43 pbhagavatula
2020-01-15 11:33 ` 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=CALBAE1NRcwBticxP8g5RPkMo5unSp0QSRzdQZd2hKRtu8wqNnA@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.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).