u-boot-amlogic.groups.io archive mirror
 help / color / mirror / Atom feed
From: "Neil Armstrong" <neil.armstrong@linaro.org>
To: Alexey Romanov <avromanov@salutedevices.com>, narmstrong@baylibre.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de,
	kernel@sberdevices.ru, Igor Prusov <ivprusov@salutedevices.com>
Subject: Re: [PATCH v1] drivers: sm: fix build warning
Date: Thu, 5 Oct 2023 14:27:51 +0200	[thread overview]
Message-ID: <3782b09f-8279-4c66-b7f6-7115ee8ce79b@linaro.org> (raw)
In-Reply-To: <20231005081936.72178-1-avromanov@salutedevices.com>

On 05/10/2023 10:19, Alexey Romanov wrote:
> This fixes following warning during u-boot build:
> WARNING: unmet direct dependencies detected for MESON_SM
>    Depends on [n]: SM [=n]
>    Selected by [y]:
>    - MESON64_COMMON [=y] && ARM [=y] && ARCH_MESON [=y]
> 
> Fixes: 9849712e7655 ("drivers: introduce Meson Secure Monitor driver")
> 
> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> Signed-off-by: Igor Prusov <ivprusov@salutedevices.com>
> ---
>   drivers/sm/Kconfig | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/sm/Kconfig b/drivers/sm/Kconfig
> index b4cc3f768e..f0987275d2 100644
> --- a/drivers/sm/Kconfig
> +++ b/drivers/sm/Kconfig
> @@ -3,7 +3,7 @@ config SM
>   
>   config MESON_SM
>   	bool "Amlogic Secure Monitor driver"
> -	depends on SM
> +	select SM
>   	default n
>   	help
>   	  Say y here to enable the Amlogic secure monitor driver.

Thanks,

Squashed into 9849712e7655 ("drivers: introduce Meson Secure Monitor driver")

Neil

      reply	other threads:[~2023-10-05 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  8:19 [PATCH v1] drivers: sm: fix build warning Alexey Romanov
2023-10-05 12:27 ` Neil Armstrong [this message]

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=3782b09f-8279-4c66-b7f6-7115ee8ce79b@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=avromanov@salutedevices.com \
    --cc=ivprusov@salutedevices.com \
    --cc=kernel@sberdevices.ru \
    --cc=narmstrong@baylibre.com \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.denx.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).