All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxs: constify platform_suspend_ops
Date: Fri, 22 Sep 2017 13:01:39 +0800	[thread overview]
Message-ID: <20170922050137.GA26358@dragon> (raw)
In-Reply-To: <be1c12e8040201dcabec64561ec6e446e2111b1e.1504111357.git.arvind.yadav.cs@gmail.com>

On Wed, Aug 30, 2017 at 10:17:51PM +0530, Arvind Yadav wrote:
> platform_suspend_ops are not supposed to change at runtime.
> Functions suspend_set_ops working with const platform_suspend_ops.
> So mark the non-const structs as const.
> 
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: kernel@pengutronix.de, fabio.estevam@nxp.com,
	linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mxs: constify platform_suspend_ops
Date: Fri, 22 Sep 2017 13:01:39 +0800	[thread overview]
Message-ID: <20170922050137.GA26358@dragon> (raw)
In-Reply-To: <be1c12e8040201dcabec64561ec6e446e2111b1e.1504111357.git.arvind.yadav.cs@gmail.com>

On Wed, Aug 30, 2017 at 10:17:51PM +0530, Arvind Yadav wrote:
> platform_suspend_ops are not supposed to change at runtime.
> Functions suspend_set_ops working with const platform_suspend_ops.
> So mark the non-const structs as const.
> 
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>

Applied, thanks.

  reply	other threads:[~2017-09-22  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 16:47 [PATCH] ARM: mxs: constify platform_suspend_ops Arvind Yadav
2017-08-30 16:47 ` Arvind Yadav
2017-09-22  5:01 ` Shawn Guo [this message]
2017-09-22  5:01   ` Shawn Guo

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=20170922050137.GA26358@dragon \
    --to=shawnguo@kernel.org \
    --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.