linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linaro.org>
To: Ohad Ben-Cohen <ohad@wizery.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-remoteproc@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Baolin Wang <baolin.wang@linaro.org>
Subject: Re: [PATCH] hwspinlock: Change hwspinlock to a bool
Date: Tue, 14 Nov 2017 20:58:18 +0800	[thread overview]
Message-ID: <CAMz4kuKeqOH7m0zx7=rmaBOg5eekw3RZZwsREOJCC0sVotG40g@mail.gmail.com> (raw)
In-Reply-To: <2d10549b83f8b4990af60a61b44514b47da4c287.1509777293.git.baolin.wang@linaro.org>

Hi Bjorn,

On 4 November 2017 at 14:37, Baolin Wang <baolin.wang@linaro.org> wrote:
> Change hwspinlock to a bool in case some drivers will meet dependency
> issue when hwspinlock is built as a module.
>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>

Could you apply this patch into K4.15 if there are no other comments? Thanks.

> ---
>  drivers/hwspinlock/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
> index 6e0a553..f0f4679 100644
> --- a/drivers/hwspinlock/Kconfig
> +++ b/drivers/hwspinlock/Kconfig
> @@ -3,7 +3,7 @@
>  #
>
>  menuconfig HWSPINLOCK
> -       tristate "Hardware Spinlock drivers"
> +       bool "Hardware Spinlock drivers"
>
>  config HWSPINLOCK_OMAP
>         tristate "OMAP Hardware Spinlock device"
> --
> 1.9.1
>



-- 
Baolin.wang
Best Regards

  reply	other threads:[~2017-11-14 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04  6:37 [PATCH] hwspinlock: Change hwspinlock to a bool Baolin Wang
2017-11-14 12:58 ` Baolin Wang [this message]
2017-11-14 15:03   ` Mark Brown
2017-11-15  2:07     ` Baolin Wang

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='CAMz4kuKeqOH7m0zx7=rmaBOg5eekw3RZZwsREOJCC0sVotG40g@mail.gmail.com' \
    --to=baolin.wang@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.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;
as well as URLs for NNTP newsgroup(s).