patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Mordechay Haimovsky <motih@mellanox.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix build with old kernels
Date: Wed, 15 Aug 2018 17:25:21 +0000	[thread overview]
Message-ID: <B9066CE2-244C-452F-BA97-A01D8BC3228E@mellanox.com> (raw)
In-Reply-To: <1534352570-12902-1-git-send-email-motih@mellanox.com>


> On Aug 15, 2018, at 10:02 AM, Mordechay Haimovsky <motih@mellanox.com> wrote:
> 
> This commit fixes compilation errors due to missing definitions
> found when compiling mlx5 PMD from DPDK 17.11-LTS on Ubuntu 12.4
> with kernel 3.15.
> 
> Fixes: 75ef62a94301 ("net/mlx5: fix link speed capability information")
> Fixes: 5bfc9fc112dd ("net/mlx5: use static assert for compile-time sanity checks")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
> ---

Applied to stable/17.11

Thanks,
Yongseok

      reply	other threads:[~2018-08-15 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 17:02 Moti Haimovsky
2018-08-15 17:25 ` Yongseok Koh [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=B9066CE2-244C-452F-BA97-A01D8BC3228E@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=motih@mellanox.com \
    --cc=stable@dpdk.org \
    /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).