All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Angelo Dureghello <angelo@kernel-space.org>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"Linux/m68k" <linux-m68k@vger.kernel.org>,
	linux-can@vger.kernel.org, Joakim Zhang <qiangqing.zhang@nxp.com>
Subject: Re: [PATCH v3 4/5] can: flexcan: update Kconfig to allow non-of cases
Date: Mon, 21 Jun 2021 22:11:58 +0200	[thread overview]
Message-ID: <CAMuHMdV8a=YKowGLY3kGqwsfAPd3VPEXS8x7xqYaUz9ZBh64hg@mail.gmail.com> (raw)
In-Reply-To: <20210621184615.3345846-4-angelo@kernel-space.org>

Hi Angelo,

On Mon, Jun 21, 2021 at 8:47 PM Angelo Dureghello
<angelo@kernel-space.org> wrote:
> Update flexcan to support architectures without fdt.
>
> Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
> ---
> Changes for v2:
> none
> Changes for v3:
> - change to just remove OF
> ---
>  drivers/net/can/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
> index e355d3974977..a0f4ae7ccb84 100644
> --- a/drivers/net/can/Kconfig
> +++ b/drivers/net/can/Kconfig
> @@ -97,7 +97,7 @@ config CAN_AT91
>
>  config CAN_FLEXCAN
>         tristate "Support for Freescale FLEXCAN based chips"
> -       depends on OF && HAS_IOMEM
> +       depends on HAS_IOMEM

I think you want to add a line

    depends on ARCH_LAYERSCAPE || ARCH_MXC || COLDFIRE ||
FSL_SOC_BOOKE || COMPILE_TEST

(or PPC instead of FSL_SOC_BOOKE?)
so the question doesn't pop up when compiling a kernel for a system
that cannot have a Freescale FlexCAN IP block.

>         help
>           Say Y here if you want to support for Freescale FlexCAN.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-06-21 20:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:46 [PATCH v3 1/5] can: flexcan: add platform data header Angelo Dureghello
2021-06-21 18:46 ` [PATCH v3 2/5] m68k: stmark2: update board setup Angelo Dureghello
2021-06-21 18:46 ` [PATCH v3 3/5] m68k: m5441x: add flexcan support Angelo Dureghello
2021-06-21 18:46 ` [PATCH v3 4/5] can: flexcan: update Kconfig to allow non-of cases Angelo Dureghello
2021-06-21 20:11   ` Geert Uytterhoeven [this message]
2021-06-21 20:18     ` Marc Kleine-Budde
2021-06-21 20:22       ` Geert Uytterhoeven
2021-06-21 20:41         ` Marc Kleine-Budde
2021-06-22  6:52           ` Geert Uytterhoeven
2021-06-22  6:54             ` Marc Kleine-Budde
2021-06-26 12:18               ` Angelo Dureghello
2021-06-21 18:46 ` [PATCH v3 5/5] can: flexcan: add mcf5441x support Angelo Dureghello
2021-06-21 19:19   ` Marc Kleine-Budde
2021-06-27 14:54     ` Angelo Dureghello
2021-06-21 18:59 ` [PATCH v3 1/5] can: flexcan: add platform data header Marc Kleine-Budde

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='CAMuHMdV8a=YKowGLY3kGqwsfAPd3VPEXS8x7xqYaUz9ZBh64hg@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=angelo@kernel-space.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=qiangqing.zhang@nxp.com \
    --cc=wg@grandegger.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 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.