From: Jerin Jacob <jerinjacobk@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
David Marchand <david.marchand@redhat.com>,
stable@dpdk.org
Subject: Re: [PATCH v5 2/2] eventdev: fix missing driver names in info struct
Date: Thu, 19 Oct 2023 11:05:47 +0530 [thread overview]
Message-ID: <CALBAE1O3hhwQNFh0tAONj1LBP7eS+68TJMqxhVRPQNsnSYP6EA@mail.gmail.com> (raw)
In-Reply-To: <20231018133932.150177-2-bruce.richardson@intel.com>
On Wed, Oct 18, 2023 at 9:07 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> Rather than relying on the individual drivers to always populated the
> driver name field in the info structure - something missed by some
> drivers, we can do so in the eventdev rte_event_dev_info_get() function.
> This fixes issues
>
> Fixes: bbbb929da5e6 ("event/skeleton: add skeleton eventdev driver")
> Fixes: 0ce3ce7c275c ("event/dpaa2: add configuration functions")
> Cc: stable@dpdk.org
>
> Suggested-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Series applied to dpdk-next--eventdev/for-main. Thanks
prev parent reply other threads:[~2023-10-19 5:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 15:17 [PATCH] event/sw: fix missing device pointer Bruce Richardson
2023-10-17 12:45 ` Van Haaren, Harry
2023-10-17 15:51 ` [PATCH v2 1/2] " Bruce Richardson
2023-10-17 15:51 ` [PATCH v2 2/2] event/dsw: " Bruce Richardson
[not found] ` <20231017164610.191852-1-bruce.richardson@intel.com>
2023-10-17 16:46 ` [PATCH v3 1/4] event/sw: " Bruce Richardson
2023-10-17 16:46 ` [PATCH v3 2/4] event/dsw: " Bruce Richardson
2023-10-18 6:27 ` Mattias Rönnblom
2023-10-17 16:46 ` [PATCH v3 3/4] event/skeleton: " Bruce Richardson
2023-10-17 16:46 ` [PATCH v3 4/4] event/skeleton: set driver name string Bruce Richardson
2023-10-18 12:25 ` [PATCH v4 1/2] event/*: set device pointer for vdev-based eventdevs Bruce Richardson
2023-10-18 12:25 ` [PATCH v4 2/2] event/skeleton: set driver name string Bruce Richardson
2023-10-18 12:44 ` David Marchand
2023-10-18 12:52 ` Bruce Richardson
2023-10-18 13:42 ` Bruce Richardson
2023-10-18 13:01 ` [PATCH v4 1/2] event/*: set device pointer for vdev-based eventdevs David Marchand
2023-10-18 13:39 ` [PATCH v5 1/2] eventdev: fix " Bruce Richardson
2023-10-18 13:39 ` [PATCH v5 2/2] eventdev: fix missing driver names in info struct Bruce Richardson
2023-10-19 5:35 ` 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=CALBAE1O3hhwQNFh0tAONj1LBP7eS+68TJMqxhVRPQNsnSYP6EA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@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).