From: Akhil Goyal <gakhil@marvell.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"hernan.vargas@intel.com" <hernan.vargas@intel.com>
Subject: RE: [EXT] [PATCH v1 1/1] baseband/acc100: fix to input error related to padding
Date: Tue, 8 Nov 2022 05:41:47 +0000 [thread overview]
Message-ID: <CO6PR18MB44843C7437E3500A40EF5E3ED83F9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221107234532.20775-2-nicolas.chautru@intel.com>
> Previous commit includes some padding for some cases,
> which may cause input warning from the HW
> which should be safely ignored to avoid false alarm.
>
> Fixes: 6f3325bbfa ("baseband/acc100: add LDPC encoder padding function")
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
Applied to dpdk-next-crypto.
next prev parent reply other threads:[~2022-11-08 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 23:45 [PATCH v1 0/1] baseband/acc100: fix for RC2 Nicolas Chautru
2022-11-07 23:45 ` [PATCH v1 1/1] baseband/acc100: fix to input error related to padding Nicolas Chautru
2022-11-08 5:41 ` Akhil Goyal [this message]
2022-11-08 13:41 ` Maxime Coquelin
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=CO6PR18MB44843C7437E3500A40EF5E3ED83F9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@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 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).