From: Greg Ungerer <gerg@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
arnd@kernel.org, Greg Ungerer <gerg@linux-m68k.org>,
dmaengine@vger.kernel.org, linux-can@vger.kernel.org,
linux-spi@vger.kernel.org, olteanv@gmail.com,
adureghello@baylibre.com
Subject: Re: [RFC 4/4] m68k: coldfire: fix non-standard readX()/writeX() functions
Date: Fri, 8 May 2026 00:33:40 +1000 [thread overview]
Message-ID: <7bc9e2c2-3646-43bc-8405-c4367d99d8bc@kernel.org> (raw)
In-Reply-To: <20260507-masterful-pegasus-of-science-c408e0-mkl@pengutronix.de>
On 7/5/26 23:30, Marc Kleine-Budde wrote:
> On 07.05.2026 00:26:48, Greg Ungerer wrote:
>> diff --git a/drivers/net/can/flexcan/flexcan-core.c b/drivers/net/can/flexcan/flexcan-core.c
>> index f5d22c61503f..a682f02d2c43 100644
>> --- a/drivers/net/can/flexcan/flexcan-core.c
>> +++ b/drivers/net/can/flexcan/flexcan-core.c
>> @@ -296,6 +296,7 @@ static_assert(sizeof(struct flexcan_regs) == 0x4 * 18 + 0xfb8);
>> static const struct flexcan_devtype_data fsl_mcf5441x_devtype_data = {
>> .quirks = FLEXCAN_QUIRK_BROKEN_PERR_STATE |
>
> Nitpick:
> Can you move it here, so that the quirks stay sorted?
Yep, sure thing.
> FLEXCAN_QUIRK_DEFAULT_BIG_ENDIAN |
>
>> FLEXCAN_QUIRK_NR_IRQ_3 | FLEXCAN_QUIRK_NR_MB_16 |
>> + FLEXCAN_QUIRK_DEFAULT_BIG_ENDIAN |
>> FLEXCAN_QUIRK_SUPPORT_RX_MAILBOX |
>> FLEXCAN_QUIRK_SUPPORT_RX_FIFO,
>> };
>
> With that change:
>
> Acked-by: Marc Kleine-Budde <mkl@pengutronix.de> # for drivers/net/can/flexcan
Thanks
Greg
prev parent reply other threads:[~2026-05-07 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260506142644.3234270-2-gerg@kernel.org>
2026-05-06 14:26 ` [RFC 4/4] m68k: coldfire: fix non-standard readX()/writeX() functions Greg Ungerer
2026-05-06 16:14 ` Frank Li
2026-05-06 19:12 ` Arnd Bergmann
2026-05-07 12:43 ` Greg Ungerer
2026-05-07 12:59 ` Arnd Bergmann
2026-05-07 13:30 ` Marc Kleine-Budde
2026-05-07 14:33 ` Greg Ungerer [this message]
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=7bc9e2c2-3646-43bc-8405-c4367d99d8bc@kernel.org \
--to=gerg@kernel.org \
--cc=adureghello@baylibre.com \
--cc=arnd@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gerg@linux-m68k.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-spi@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olteanv@gmail.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