From: Akhil Goyal <akhil.goyal@nxp.com>
To: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Srikanth Jampala <jsrikanth@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/nitrox: add 3DES-CBC support
Date: Sun, 5 Apr 2020 17:02:05 +0000 [thread overview]
Message-ID: <VE1PR04MB66398F824C9E06A1CF376D41E6C50@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR18MB2797D7F2F6FA3EFF67BE8F04D6C70@MN2PR18MB2797.namprd18.prod.outlook.com>
> > > > --
> > > > >
> > > > > This patch adds 3DES CBC mode cipher algorithm.
> > > > >
> > > > > Signed-off-by: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
> > > > > ---
> > > > Is it worth mentioning in release notes?
> > >
> > > I added that description to avoid below checkpatch warning:
> > >
> > > ### crypto/nitrox: add 3DES-CBC support
> > >
> > > WARNING:COMMIT_MESSAGE: Missing commit description - Add an
> > > appropriate one
> > >
> > > total: 0 errors, 1 warnings, 83 lines checked
> > >
> > > 0/1 valid patch
> >
> > I think you misinterpreted my comment.
> > I was talking about release notes and not patch description.
>
> I haven't added that description in the release notes.
> I only added description in the Limitations section.
OK, it seems you do not want to add this in release notes.
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2020-04-05 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 11:43 Nagadheeraj Rottela
2020-03-25 18:48 ` Akhil Goyal
2020-03-27 6:38 ` Nagadheeraj Rottela
2020-04-01 14:08 ` Akhil Goyal
2020-04-03 9:20 ` Nagadheeraj Rottela
2020-04-05 17:02 ` 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=VE1PR04MB66398F824C9E06A1CF376D41E6C50@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=jsrikanth@marvell.com \
--cc=rnagadheeraj@marvell.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).