patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Nick Connolly <nick.connolly@mayadata.io>
To: Tal Shnaiderman <talshn@nvidia.com>, dev@dpdk.org
Cc: thomas@monjalon.net, dmitry.kozliuk@gmail.com,
	navasile@linux.microsoft.com, dmitrym@microsoft.com,
	pallavi.kadam@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] eal/windows: revert definition of ETOOMANYREFS
Date: Thu, 19 Nov 2020 16:03:41 +0000	[thread overview]
Message-ID: <6ad697bb-9ebc-ffe7-61c3-4652e9b2f075@mayadata.io> (raw)
In-Reply-To: <20201119154310.16824-1-talshn@nvidia.com>

Reviewed-by: Nick Connolly <nick.connolly@mayadata.io>

On 19/11/2020 15:43, Tal Shnaiderman wrote:
> This reverts commit c917b54b0c743c7a570a4d8df8954c61d8b818c4.
>
> The definition of ETOOMANYREFS is reverted as it breaks build of
> external applications already defining it.
>
> Fixes: c917b54b0c ("eal/windows: add definition of ETOOMANYREFS")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> ---
>   lib/librte_eal/windows/include/rte_os.h | 2 --
>   1 file changed, 2 deletions(-)
>
> diff --git a/lib/librte_eal/windows/include/rte_os.h b/lib/librte_eal/windows/include/rte_os.h
> index 8300ea483a..569ed92d51 100644
> --- a/lib/librte_eal/windows/include/rte_os.h
> +++ b/lib/librte_eal/windows/include/rte_os.h
> @@ -51,8 +51,6 @@ extern "C" {
>   /* as in <windows.h> */
>   typedef long long ssize_t;
>   
> -#define ETOOMANYREFS 10059 /* WSAETOOMANYREFS */
> -
>   #ifndef RTE_TOOLCHAIN_GCC
>   
>   static inline int


  reply	other threads:[~2020-11-19 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 15:43 Tal Shnaiderman
2020-11-19 16:03 ` Nick Connolly [this message]
2020-11-20  9:12 ` David Marchand
2020-11-20  9:17   ` David Marchand

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=6ad697bb-9ebc-ffe7-61c3-4652e9b2f075@mayadata.io \
    --to=nick.connolly@mayadata.io \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=navasile@linux.microsoft.com \
    --cc=pallavi.kadam@intel.com \
    --cc=stable@dpdk.org \
    --cc=talshn@nvidia.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).