From: Su <suyanjun218@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
manivannan.sadhasivam@linaro.org, thomas.kopp@microchip.com,
wg@grandegger.com, davem@davemloft.net, kuba@kernel.org,
lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] can: mcp251xfd: use regmap_bulk_write for compatibility
Date: Fri, 22 Jan 2021 15:59:22 +0800 [thread overview]
Message-ID: <a19c70eb-6478-836a-8b39-be34101bdcae@gmail.com> (raw)
In-Reply-To: <7007275e-a271-8160-729b-67e4d579dfe2@pengutronix.de>
在 2021/1/22 下午3:26, Marc Kleine-Budde 写道:
> On 1/22/21 4:02 AM, Su Yanjun wrote:
>> Recently i use mcp2518fd on 4.x kernel which multiple write is not
>> backported, regmap_raw_write will cause old kernel crash because the
>> tx buffer in driver is smaller then 2K. Use regmap_bulk_write instead
>> for compatibility.
> Hmmm, this patch will never be backported to any 4.x kernel, as the driver is
> not available on these kernels. You have to carry patches for these kernels
> anyway, so I think I'll not take that patch. Sorry. Drop me a note if you are
> interested in updating your kernel to a recent v5.11 kernel.
I got it. I have already port it to 4.x kernel. I just want anyone
working on old kernels to use the driver more easier.
Thanks.
>
> regards,
> Marc
>
next prev parent reply other threads:[~2021-01-22 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 3:02 [PATCH v1] can: mcp251xfd: use regmap_bulk_write for compatibility Su Yanjun
2021-01-22 7:26 ` Marc Kleine-Budde
2021-01-22 7:59 ` Su [this message]
2021-01-22 8:14 ` 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=a19c70eb-6478-836a-8b39-be34101bdcae@gmail.com \
--to=suyanjun218@gmail.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=thomas.kopp@microchip.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).