From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Angelo Dureghello <angelo@kernel-space.org>,
wg@grandegger.com, geert@linux-m68k.org,
linux-m68k@vger.kernel.org, linux-can@vger.kernel.org,
qiangqing.zhang@nxp.com
Subject: Re: [PATCH v5 3/5] m68k: m5441x: add flexcan support
Date: Wed, 14 Jul 2021 21:38:54 +0200 [thread overview]
Message-ID: <20210714193854.dq2seoew4n35b4xv@pengutronix.de> (raw)
In-Reply-To: <1a95b055-5d14-f43e-81dd-d0a0ddbdb1f1@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On 12.07.2021 14:33:42, Greg Ungerer wrote:
[...]
> That way the timing of patches 1, 4 and 5 being applied doesn't matter.
> There is no way to enable CONFIG_CAN_FLEXCAN until patch 4 is applied.
> (And you probably should have swapped the order of patches 4 and 5, so that
> the Kconfig change is the last in the series.)
Done - I've changed the order of 4 and 5.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-14 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 9:48 [PATCH v5 1/5] can: flexcan: add platform data header Angelo Dureghello
2021-07-02 9:48 ` [PATCH v5 2/5] m68k: stmark2: update board setup Angelo Dureghello
2021-07-02 9:48 ` [PATCH v5 3/5] m68k: m5441x: add flexcan support Angelo Dureghello
2021-07-12 4:33 ` Greg Ungerer
2021-07-14 19:38 ` Marc Kleine-Budde [this message]
2021-07-20 18:53 ` Angelo Dureghello
2021-07-20 23:00 ` Greg Ungerer
2021-07-21 10:04 ` Angelo Dureghello
2021-07-02 9:48 ` [PATCH v5 4/5] can: flexcan: update Kconfig to enable coldfire Angelo Dureghello
2021-07-02 9:48 ` [PATCH v5 5/5] can: flexcan: add mcf5441x support Angelo Dureghello
2021-07-02 9:54 ` [PATCH v5 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=20210714193854.dq2seoew4n35b4xv@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=angelo@kernel-space.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--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 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).