The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Joe Perches" <joe@perches.com>,
	linux-kernel@vger.kernel.org,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [PATCH] const_structs.checkpatch: add pinctrl_ops and pinmux_ops
Date: Mon, 31 Aug 2020 14:47:31 +0530	[thread overview]
Message-ID: <20200831091731.GB4154@mani> (raw)
In-Reply-To: <20200830224352.37114-1-rikard.falkeborn@gmail.com>

On 0831, Rikard Falkeborn wrote:
> All usages of include/linux of these are const pointers, and all
> instances in the kernel except one, that are not const can be made
> const (patches have been posted for those separately).
> 
> Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>

Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>

Thanks,
Mani

> ---
>  scripts/const_structs.checkpatch | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/scripts/const_structs.checkpatch b/scripts/const_structs.checkpatch
> index cd45cb3c2b04..1aae4f4fdacc 100644
> --- a/scripts/const_structs.checkpatch
> +++ b/scripts/const_structs.checkpatch
> @@ -40,6 +40,8 @@ nvkm_device_chip
>  of_device_id
>  pci_raw_ops
>  phy_ops
> +pinctrl_ops
> +pinmux_ops
>  pipe_buf_operations
>  platform_hibernation_ops
>  platform_suspend_ops
> -- 
> 2.28.0
> 

  reply	other threads:[~2020-08-31  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 22:43 [PATCH] const_structs.checkpatch: add pinctrl_ops and pinmux_ops Rikard Falkeborn
2020-08-31  9:17 ` Manivannan Sadhasivam [this message]
2020-09-12 10: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=20200831091731.GB4154@mani \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=afaerber@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rikard.falkeborn@gmail.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