From: Hauke Mehrtens <hauke@hauke-m.de>
To: Stefan Assmann <sassmann@kpanic.de>, mcgrof@do-not-panic.com
Cc: backports@vger.kernel.org
Subject: Re: [PATCH] backports: include gpio consumer.h
Date: Thu, 17 Jul 2014 22:42:44 +0200 [thread overview]
Message-ID: <53C83544.7030306@hauke-m.de> (raw)
In-Reply-To: <1404999110-13791-1-git-send-email-sassmann@kpanic.de>
On 07/10/2014 03:31 PM, Stefan Assmann wrote:
> While doing a make allmodconfig I noticed the following:
> CC [M] /dev/shm/backports-next/drivers/media/i2c/adv7604.o
> /dev/shm/backports-next/drivers/media/i2c/adv7604.c:31:33: fatal error: linux/gpio/consumer.h: No such file or directory
>
> Including the header fixes the error.
>
> Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
> ---
> copy-list | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/copy-list b/copy-list
> index 7ad8972..b52e9f2 100644
> --- a/copy-list
> +++ b/copy-list
> @@ -107,6 +107,10 @@ drivers/net/ethernet/intel/Kconfig
> drivers/net/ethernet/intel/Makefile
> drivers/net/ethernet/intel/igb/
>
> +# gpio
> +include/linux/gpio/
> +include/linux/gpio/consumer.h
> +
> # wwan drivers
> include/uapi/linux/usb/cdc.h
> include/uapi/linux/usb/cdc-wdm.h
>
Is this correct? backports does not provide the implementation of the
functions in include/linux/gpio/consumer.h and it will result in hard to
debug problems with some function signature is different in our version
of consumer.h and the version in the kernel.
I am against backporting this and would add an empty version of this header.
Hauke
next prev parent reply other threads:[~2014-07-17 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 13:31 [PATCH] backports: include gpio consumer.h Stefan Assmann
2014-07-17 20:23 ` Luis R. Rodriguez
2014-07-17 20:42 ` Hauke Mehrtens [this message]
2014-07-17 21:27 ` Luis R. Rodriguez
2014-07-18 7:41 ` Stefan Assmann
2014-07-19 16:17 ` Hauke Mehrtens
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=53C83544.7030306@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=sassmann@kpanic.de \
/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.