From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
Tal Shnaiderman <talshn@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/4] common/mlx5: add missing SPDX tag for windows headers
Date: Wed, 19 May 2021 10:36:51 +0200 [thread overview]
Message-ID: <9374617.YPN1BMlsdI@thomas> (raw)
In-Reply-To: <DM6PR12MB39452FA3FB4E84C786CA11E7A46A9@DM6PR12MB3945.namprd12.prod.outlook.com>
> > These files were added without requires SPDX headers.
> >
> > Fixes: 7525ebd8ebb0 ("common/mlx5: add glue functions on Windows")
> > Cc: talshn@nvidia.com
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > -/*
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > * Copyright (C) Mellanox Technologies, Ltd. 2001-2020.
> > - *
> > */
> > +
> > #ifndef __MLX5_WIN_ETX_H__
> > #define __MLX5_WIN_ETX_H__
> >
> > --
> > 2.30.2
>
> Thanks Stephen,
>
> Doesn't this patch needs to cc stable as well since those files were added in 21.02?
>
> Acked-by: Tal Shnaiderman <talshn@nvidia.com>
Yes will add stable while applying.
next prev parent reply other threads:[~2021-05-19 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 21:00 [dpdk-dev] [PATCH 0/4] Cleanup last remaining SPDX issues Stephen Hemminger
2021-03-16 21:00 ` [dpdk-dev] [PATCH 1/4] common/mlx5: add missing SPDX tag for windows headers Stephen Hemminger
2021-03-17 9:15 ` Tal Shnaiderman
2021-05-19 8:36 ` Thomas Monjalon [this message]
2021-03-16 21:00 ` [dpdk-dev] [PATCH 2/4] devtools/check-spdx-tag.sh: ignore JSON files Stephen Hemminger
2021-03-16 21:00 ` [dpdk-dev] [PATCH 3/4] doc: add SPDX tag to custom CSS file Stephen Hemminger
2021-05-19 8:44 ` Thomas Monjalon
2021-03-16 21:00 ` [dpdk-dev] [PATCH 4/4] app/test: remove license boilerplate Stephen Hemminger
2021-05-19 8:46 ` [dpdk-dev] [PATCH 0/4] Cleanup last remaining SPDX issues Thomas Monjalon
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=9374617.YPN1BMlsdI@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=talshn@nvidia.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).