From: Akhil Goyal <gakhil@marvell.com>
To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Ciara Power <ciara.power@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Kai Ji" <kai.ji@intel.com>, "Fan Zhang" <fanzhang.oss@gmail.com>
Subject: RE: [EXT] Re: [PATCH v2] cryptodev: fix device socket ID type
Date: Wed, 5 Jul 2023 18:23:40 +0000 [thread overview]
Message-ID: <CO6PR18MB44844B18C073278C53745DD9D82FA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <fc79543c-e4ed-ca8b-9cde-a691306861a1@yandex.ru>
> 05/07/2023 11:36, Ciara Power пишет:
> > The socket ID field for a cryptodev device data was unsigned int.
> > Due to recent changes to the default device socket ID,
> > this caused an issue when the socket ID was unknown and set to -1.
> > The device socket ID wrapped around to 255,
> > and caused errors when allocating memory.
> >
> > Changing this field type to int fixes the issue, as it now takes the
> > correct -1 value.
> >
> > Fixes: 7dcd73e37965 ("drivers/bus: set device NUMA node to unknown by
> default")
> > Cc: olivier.matz@6wind.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> > Acked-by: Kai Ji <kai.ji@intel.com>
> >
> Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-07-05 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:21 [PATCH] " Ciara Power
2023-07-04 22:30 ` Ji, Kai
2023-07-05 9:44 ` Morten Brørup
2023-07-05 10:36 ` [PATCH v2] " Ciara Power
2023-07-05 11:29 ` Konstantin Ananyev
2023-07-05 18:23 ` Akhil Goyal [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=CO6PR18MB44844B18C073278C53745DD9D82FA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=kai.ji@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@6wind.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).