From: Yuehaibing <yuehaibing@huawei.com>
To: <support.opensource@diasemi.com>, <linus.walleij@linaro.org>,
<Adam.Thomson.Opensource@diasemi.com>, <m.felsch@pengutronix.de>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] pinctrl: da9062: Fix error gpiolib.h path
Date: Fri, 28 Feb 2020 14:30:34 +0800 [thread overview]
Message-ID: <a28de19d-7e44-1583-e436-b45456b2e62c@huawei.com> (raw)
In-Reply-To: <20200228040047.14808-1-yuehaibing@huawei.com>
Sorry, pls ignore this, will resend v2.
On 2020/2/28 12:00, YueHaibing wrote:
> drivers/pinctrl/pinctrl-da9062.c:28:10: fatal error: ../gpio/gpiolib.h: No such file or directory
> #include <../gpio/gpiolib.h>
> ^~~~~~~~~~~~~~~~~~~
>
> Fix this wrong include path.
>
> Fixes: 56cc3af4e8c8 ("pinctrl: da9062: add driver support")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/pinctrl/pinctrl-da9062.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/pinctrl-da9062.c b/drivers/pinctrl/pinctrl-da9062.c
> index f704ee0b2fd9..c15eb6e99bc1 100644
> --- a/drivers/pinctrl/pinctrl-da9062.c
> +++ b/drivers/pinctrl/pinctrl-da9062.c
> @@ -25,7 +25,7 @@
> * We need this get the gpio_desc from a <gpio_chip,offset> tuple to decide if
> * the gpio is active low without a vendor specific dt-binding.
> */
> -#include <../gpio/gpiolib.h>
> +#include "../../gpio/gpiolib.h"
>
> #define DA9062_TYPE(offset) (4 * (offset % 2))
> #define DA9062_PIN_SHIFT(offset) (4 * (offset % 2))
>
next prev parent reply other threads:[~2020-02-28 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 4:00 YueHaibing
2020-02-28 6:30 ` Yuehaibing [this message]
2020-02-28 6:34 ` [PATCH v2 " YueHaibing
2020-02-28 6:59 ` Marco Felsch
2020-02-28 13:16 ` Linus Walleij
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=a28de19d-7e44-1583-e436-b45456b2e62c@huawei.com \
--to=yuehaibing@huawei.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=support.opensource@diasemi.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
all inboxes | Powered by JetHome®