From: Greg Ungerer <gerg@linux-m68k.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Angelo Dureghello <angelo@kernel-space.org>
Cc: wg@grandegger.com, geert@linux-m68k.org,
linux-m68k@vger.kernel.org, linux-can@vger.kernel.org,
qiangqing.zhang@nxp.com
Subject: Re: [PATCH v4 2/5] m68k: stmark2: update board setup
Date: Thu, 1 Jul 2021 17:41:04 +1000 [thread overview]
Message-ID: <7effec9f-e3aa-12d1-fc91-cb7b2c4ae9ab@linux-m68k.org> (raw)
In-Reply-To: <20210701065327.maawrm546dkfzxbx@pengutronix.de>
On 1/7/21 4:53 pm, Marc Kleine-Budde wrote:
> On 01.07.2021 01:00:13, Angelo Dureghello wrote:
>> Add configuration for flexcan pads.
>>
>> Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
>
> How do we upstream the m68k changes? Should we split this series into
> m68k and CAN?
I am happy to take the m68k specific changes (patches 2 and 3)
through the m68knommu git tree.
Regards
Greg
next prev parent reply other threads:[~2021-07-01 7:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 23:00 [PATCH v4 1/5] can: flexcan: add platform data header Angelo Dureghello
2021-06-30 23:00 ` [PATCH v4 2/5] m68k: stmark2: update board setup Angelo Dureghello
2021-07-01 6:53 ` Marc Kleine-Budde
2021-07-01 7:41 ` Greg Ungerer [this message]
2021-07-01 7:42 ` Marc Kleine-Budde
2021-07-01 8:02 ` Greg Ungerer
2021-07-01 9:10 ` Geert Uytterhoeven
2021-07-01 9:37 ` Marc Kleine-Budde
2021-07-02 9:35 ` Angelo Dureghello
2021-06-30 23:00 ` [PATCH v4 3/5] m68k: m5441x: add flexcan support Angelo Dureghello
2021-06-30 23:00 ` [PATCH v4 4/5] can: flexcan: update Kconfig to enable coldfire Angelo Dureghello
2021-07-01 9:02 ` Marc Kleine-Budde
2021-06-30 23:00 ` [PATCH v4 5/5] can: flexcan: add mcf5441x support Angelo Dureghello
2021-07-01 6:50 ` Marc Kleine-Budde
2021-07-01 9:27 ` [PATCH v4 1/5] can: flexcan: add platform data header Marc Kleine-Budde
2021-07-02 9:21 ` Angelo Dureghello
2021-07-02 9:55 ` 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=7effec9f-e3aa-12d1-fc91-cb7b2c4ae9ab@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=angelo@kernel-space.org \
--cc=geert@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.