From: Angelo Dureghello <angelo@kernel-space.org>
To: Greg Ungerer <gerg@linux-m68k.org>,
wg@grandegger.com, mkl@pengutronix.de
Cc: 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, 21 Jul 2021 12:04:10 +0200 [thread overview]
Message-ID: <e1e702b8-9124-b063-a17c-217336f8c840@kernel-space.org> (raw)
In-Reply-To: <4a745955-8e43-3024-a004-0db0e084d74f@linux-m68k.org>
Hi Greg,
On 21/07/21 1:00 AM, Greg Ungerer wrote:
> Hi Angelo,
>
> On 21/7/21 4:53 am, Angelo Dureghello wrote:
>> Hi Greg,
>>
>> sorry was away for some vacation time.
>>
>> Is there still any job required here ?
>
> No :-)
> I modified the change as per my suggestions below - so I could push to
> m68knommu git tree.
> (Otherwise It does not compile). See:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git/commit/?h=for-next&id=64151620227a2fcb13dae0b99b6a1003edb38c67
>
>
Super thanks ! Will check this properly next time.
> Regards
> Greg
>
>
>
Regards,
Angelo
next prev parent reply other threads:[~2021-07-21 11:27 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
2021-07-20 18:53 ` Angelo Dureghello
2021-07-20 23:00 ` Greg Ungerer
2021-07-21 10:04 ` Angelo Dureghello [this message]
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=e1e702b8-9124-b063-a17c-217336f8c840@kernel-space.org \
--to=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=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 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).