From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 3/3] nvme-cli: fix header paths for new structure
Date: Fri, 26 Oct 2018 14:07:33 -0600 [thread overview]
Message-ID: <20181026200733.GA10403@localhost.localdomain> (raw)
In-Reply-To: <20181026170834.23457-3-chaitanya.kulkarni@wdc.com>
On Fri, Oct 26, 2018@10:08:34AM -0700, Chaitanya Kulkarni wrote:
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni at wdc.com>
> ---
> plugins/wdc/wdc-nvme.c | 16 ++++++++--------
> plugins/wdc/wdc-nvme.h | 4 ++--
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/plugins/wdc/wdc-nvme.c b/plugins/wdc/wdc-nvme.c
> index 5ef965d..d9c879c 100644
> --- a/plugins/wdc/wdc-nvme.c
> +++ b/plugins/wdc/wdc-nvme.c
> @@ -31,14 +31,14 @@
>
> #include "linux/nvme_ioctl.h"
>
> -#include "nvme.h"
> -#include "nvme-print.h"
> -#include "nvme-ioctl.h"
> -#include "plugin.h"
> -#include "json.h"
> -
> -#include "argconfig.h"
> -#include "suffix.h"
> +#include "../../nvme.h"
> +#include "../../nvme-print.h"
> +#include "../../nvme-ioctl.h"
> +#include "../../plugin.h"
> +#include "../../json.h"
> +
> +#include "../../argconfig.h"
> +#include "../../suffix.h"
The Makefile has the include path set such that this shouldn't be
necessary. Is the new directory structure causing a problem in any
environments?
next prev parent reply other threads:[~2018-10-26 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:08 [PATCH 1/3] nvme-cli: fix array len to hold string of size 4 Chaitanya Kulkarni
2018-10-26 17:08 ` [PATCH 2/3] nvme-cli: fix endianness for the structure field Chaitanya Kulkarni
2018-10-26 17:08 ` [PATCH 3/3] nvme-cli: fix header paths for new structure Chaitanya Kulkarni
2018-10-26 20:07 ` Keith Busch [this message]
2018-10-26 20:11 ` Chaitanya Kulkarni
2018-10-26 20:17 ` Keith Busch
2018-10-26 21:56 ` Chaitanya Kulkarni
2018-10-29 21:45 ` Chaitanya Kulkarni
2018-10-29 22:02 ` Keith Busch
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=20181026200733.GA10403@localhost.localdomain \
--to=keith.busch@intel.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 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.