From: Arun Muthusamy <arun.muthusamy@gaisler.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org, Daniel Hellstrom <daniel@gaisler.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mkl@pengutronix.de, mailhol@kernel.org
Subject: Re: [PATCH v5 05/16] can: grcan: Replace bit timing macros with literal values
Date: Thu, 5 Mar 2026 16:43:00 +0100 [thread overview]
Message-ID: <4399e6e5-e83f-4831-936b-58f1a03d33b5@gaisler.com> (raw)
In-Reply-To: <fa473d32-ff7c-4ca1-8caa-57eff39f79a5@kernel.org>
On 2/16/26 16:01, Krzysztof Kozlowski wrote:
> On 16/02/2026 14:53, Arun Muthusamy wrote:
>> Refactor the bit timing constants in grcan_bittiming_const by replacing
>> macros with literal values.
>>
>> Signed-off-by: Arun Muthusamy <arun.muthusamy@gaisler.com>
>> Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
> It's random DCO all over. One patch has this order, other patch has a
> reversed one.
>
> Please read submitting patches document to understand what you certify
> and THEN certify that in a way submitting patches asks you. Not other way.
>
Thank you for pointing this out. I apologize for the mistake.
I've corrected the DCO order issue, and it will be addressed in the upcoming patch series.
--
--
BR,
Arun Muthusamy
Software Engineer
Frontgrade Gaisler
T : +46 (0) 700 558 528
arun.muthusamy@gaisler.com
Frontgrade Gaisler AB, Kungsgatan 12, SE-411 19 GÖTEBORG, Sweden.
+46 (0) 31 775 8650, www.gaisler.com
next prev parent reply other threads:[~2026-03-05 15:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:53 [PATCH v5 00/16] can: grcan: Enhance driver with CANFD Support and Improvements Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 01/16] dt-bindings: Add vendor prefix for Frontgrade Gaisler AB Arun Muthusamy
2026-02-16 14:53 ` Krzysztof Kozlowski
2026-02-16 13:53 ` [PATCH v5 02/16] net: can: Convert gaisler,grcan to DT schema Arun Muthusamy
2026-02-16 14:59 ` Krzysztof Kozlowski
2026-02-16 13:53 ` [PATCH v5 03/16] MAINTAINERS: Add maintainers for GRCAN CAN network driver Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 04/16] can: grcan: Add clock handling Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 05/16] can: grcan: Replace bit timing macros with literal values Arun Muthusamy
2026-02-16 15:01 ` Krzysztof Kozlowski
2026-03-05 15:43 ` Arun Muthusamy [this message]
2026-02-16 13:53 ` [PATCH v5 06/16] can: grcan: Simplify timing configuration Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 07/16] can: grcan: add FD capability detection and nominal bit-timing Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 08/16] can: grcan: optimize DMA by 32-bit accesses Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 09/16] can: grcan: set DMA mask for GRCAN and GRCANFD to 32-bit Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 10/16] can: grcan: Add saving and restoring of CAN FD baud-rate registers Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 11/16] can: grcan: Reserve space between cap and next register to align with address layout Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 12/16] can: grcan: Refactor GRCAN DMA buffer to use structured memory layout Arun Muthusamy
2026-02-22 15:46 ` Vincent Mailhol
2026-02-16 13:53 ` [PATCH v5 13/16] can: grcan: Add CANFD TX support alongside legacy CAN Arun Muthusamy
2026-02-22 15:28 ` Vincent Mailhol
2026-02-16 13:53 ` [PATCH v5 14/16] can: grcan: Add CANFD RX " Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 15/16] can: grcan: Update echo skb handling to match variable length CANFD frame Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 16/16] can: grcan: Advertise CANFD capability Arun Muthusamy
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=4399e6e5-e83f-4831-936b-58f1a03d33b5@gaisler.com \
--to=arun.muthusamy@gaisler.com \
--cc=conor+dt@kernel.org \
--cc=daniel@gaisler.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®