linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Mayer <mmayer@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"maintainer:BROADCOM STB DPFE DRIVER" 
	<bcm-kernel-feedback-list@broadcom.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	"moderated list:BROADCOM STB DPFE DRIVER" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] memory: Allow building Broadcom STB DPFE as module
Date: Fri, 24 Sep 2021 08:27:59 -0700	[thread overview]
Message-ID: <CAGt4E5v31_Q5U7AR0uz8FKdAEAzZGdcRQNmV-cVVQrZruAZVJQ@mail.gmail.com> (raw)
In-Reply-To: <20210924031459.8911-1-f.fainelli@gmail.com>

On Thu, 23 Sept 2021 at 20:15, Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> Allow building the Broadcom STB DPFE driver as a module, it is already a
> platform driver proper with all of the resource releasing device
> managed.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

Acked-by: Markus Mayer <mmayer@broadcom.com>

Thanks!


> ---
>  drivers/memory/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/memory/Kconfig b/drivers/memory/Kconfig
> index 72c0df129d5c..0ebb83b35a64 100644
> --- a/drivers/memory/Kconfig
> +++ b/drivers/memory/Kconfig
> @@ -55,8 +55,8 @@ config ATMEL_EBI
>           SRAMs, ATA devices, etc.
>
>  config BRCMSTB_DPFE
> -       bool "Broadcom STB DPFE driver" if COMPILE_TEST
> -       default y if ARCH_BRCMSTB
> +       tristate "Broadcom STB DPFE driver"
> +       default ARCH_BRCMSTB
>         depends on ARCH_BRCMSTB || COMPILE_TEST
>         help
>           This driver provides access to the DPFE interface of Broadcom
> --
> 2.25.1
>

  reply	other threads:[~2021-09-24 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  3:14 [PATCH] memory: Allow building Broadcom STB DPFE as module Florian Fainelli
2021-09-24 15:27 ` Markus Mayer [this message]
2021-09-30 11:50 ` Krzysztof Kozlowski

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=CAGt4E5v31_Q5U7AR0uz8FKdAEAzZGdcRQNmV-cVVQrZruAZVJQ@mail.gmail.com \
    --to=mmayer@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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 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).