DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	"Michael Shamis" <michaelsh@marvell.com>,
	"Liron Himi" <lironh@marvell.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH] crypto/mvsam: fix build
Date: Thu, 16 May 2024 09:19:19 -0700	[thread overview]
Message-ID: <20240516161919.GA23478@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <20240515163415.268786-1-thomas@monjalon.net>

On Wed, May 15, 2024 at 06:34:14PM +0200, Thomas Monjalon wrote:
> When moving the alignment attribute, a semicolon was missed.
> 
> Fixes: 27595cd83053 ("drivers: move alignment attribute on types for MSVC")
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  drivers/crypto/mvsam/rte_mrvl_pmd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/crypto/mvsam/rte_mrvl_pmd.c b/drivers/crypto/mvsam/rte_mrvl_pmd.c
> index 193b7fb931..a824719fb0 100644
> --- a/drivers/crypto/mvsam/rte_mrvl_pmd.c
> +++ b/drivers/crypto/mvsam/rte_mrvl_pmd.c
> @@ -60,7 +60,7 @@ struct __rte_aligned(32) cipher_params_mapping {
>  struct __rte_aligned(32) auth_params_mapping {
>  	enum algo_supported supported;  /**< On/off switch */
>  	enum sam_auth_alg   auth_alg;   /**< Auth algorithm */
> -}
> +};

already applied i see, but acking anyway.

sorry for the trouble.

Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>

>  
>  /**
>   * Map of supported cipher algorithms.
> -- 
> 2.45.0

      parent reply	other threads:[~2024-05-16 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 16:34 Thomas Monjalon
2024-05-16  8:29 ` Thomas Monjalon
2024-05-16 16:19 ` Tyler Retzlaff [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=20240516161919.GA23478@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lironh@marvell.com \
    --cc=mb@smartsharesystems.com \
    --cc=michaelsh@marvell.com \
    --cc=thomas@monjalon.net \
    /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).