All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] mk: fix output directory name when compiling with custom kernel header dir
Date: Mon, 22 Jul 2019 10:00:59 +0200	[thread overview]
Message-ID: <2040397.ZWeezt2Vz7@xps> (raw)
In-Reply-To: <20190719170543.25259-1-herakliusz.lipiec@intel.com>

19/07/2019 19:05, Herakliusz Lipiec:
> When building dpdk with differnt kernel headers by specifying
> RTE_KERNELDIR igb_uio is compiled to directory with a name of the
> version of kernel thats running on the system instead of the one that
> dpdk is actually compiled against. Fixed by replacing hardcoded value
> with value from RTE_KERNELDIR.
> 
> Fixes: 3967af352aeb ("mk: install kernel modules")
> Cc: stable@dpdk.org
> Cc: bruce.richardson@intel.com
> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Shortened the title to: "mk: fix custom kernel directory name"
Applied, thanks




      reply	other threads:[~2019-07-22  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 13:29 [dpdk-dev] [PATCH] mk: fix output directory name when compiling with custom kernel header dir Herakliusz Lipiec
2019-07-18 13:43 ` Thomas Monjalon
2019-07-18 14:06   ` Lipiec, Herakliusz
2019-07-18 14:03 ` Herakliusz Lipiec
2019-07-18 22:25   ` Thomas Monjalon
2019-07-19 11:09     ` Lipiec, Herakliusz
2019-07-19 11:36       ` Thomas Monjalon
2019-07-19 17:01         ` Lipiec, Herakliusz
2019-07-19 11:11   ` [dpdk-dev] [PATCH v2] " Herakliusz Lipiec
2019-07-19 17:05     ` [dpdk-dev] [PATCH v3] " Herakliusz Lipiec
2019-07-22  8:00       ` Thomas Monjalon [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=2040397.ZWeezt2Vz7@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=herakliusz.lipiec@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.