All of lore.kernel.org
 help / color / mirror / Atom feed
From: sshtylyov@ru.mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: include machine header to core.h
Date: Tue, 06 Mar 2012 21:48:36 +0300	[thread overview]
Message-ID: <4F565C04.1030202@ru.mvista.com> (raw)
In-Reply-To: <1331038557-1398-1-git-send-email-linus.walleij@stericsson.com>

Hello.

On 03/06/2012 03:55 PM, Linus Walleij wrote:

> From: Linus Walleij<linus.walleij@linaro.org>

> struct pinctrl_setting contains an enum pinctrl_map_type
> field, so we need to include machine.h. Also fix kerneldoc
> to indicate that the pinctrl_setting is about both muxing
> and other config.

    I don't see where you touch kernel-doc...

> Signed-off-by: Linus Walleij<linus.walleij@linaro.org>
> ---
>   drivers/pinctrl/core.h |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)

> diff --git a/drivers/pinctrl/core.h b/drivers/pinctrl/core.h
> index 5b3ff13..42fb0ea 100644
> --- a/drivers/pinctrl/core.h
> +++ b/drivers/pinctrl/core.h
> @@ -12,6 +12,7 @@
>   #include<linux/mutex.h>
>   #include<linux/radix-tree.h>
>   #include<linux/pinctrl/pinconf.h>
> +#include<linux/pinctrl/machine.h>
>
>   struct pinctrl_gpio_range;

WBR, Sergei

WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Stephen Warren <swarren@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Haojian Zhuang <haojian.zhuang@marvell.com>,
	Thomas Abraham <thomas.abraham@linaro.org>,
	Rajendra Nayak <rajendra.nayak@linaro.org>,
	Dong Aisheng <dong.aisheng@linaro.org>,
	Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH] pinctrl: include machine header to core.h
Date: Tue, 06 Mar 2012 21:48:36 +0300	[thread overview]
Message-ID: <4F565C04.1030202@ru.mvista.com> (raw)
In-Reply-To: <1331038557-1398-1-git-send-email-linus.walleij@stericsson.com>

Hello.

On 03/06/2012 03:55 PM, Linus Walleij wrote:

> From: Linus Walleij<linus.walleij@linaro.org>

> struct pinctrl_setting contains an enum pinctrl_map_type
> field, so we need to include machine.h. Also fix kerneldoc
> to indicate that the pinctrl_setting is about both muxing
> and other config.

    I don't see where you touch kernel-doc...

> Signed-off-by: Linus Walleij<linus.walleij@linaro.org>
> ---
>   drivers/pinctrl/core.h |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)

> diff --git a/drivers/pinctrl/core.h b/drivers/pinctrl/core.h
> index 5b3ff13..42fb0ea 100644
> --- a/drivers/pinctrl/core.h
> +++ b/drivers/pinctrl/core.h
> @@ -12,6 +12,7 @@
>   #include<linux/mutex.h>
>   #include<linux/radix-tree.h>
>   #include<linux/pinctrl/pinconf.h>
> +#include<linux/pinctrl/machine.h>
>
>   struct pinctrl_gpio_range;

WBR, Sergei

  parent reply	other threads:[~2012-03-06 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 12:55 [PATCH] pinctrl: include machine header to core.h Linus Walleij
2012-03-06 12:55 ` Linus Walleij
2012-03-06 17:28 ` Stephen Warren
2012-03-06 17:28   ` Stephen Warren
2012-03-06 18:48 ` Sergei Shtylyov [this message]
2012-03-06 18:48   ` Sergei Shtylyov
2012-03-06 22:25   ` Linus Walleij
2012-03-06 22:25     ` 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=4F565C04.1030202@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-arm-kernel@lists.infradead.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.