From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH net 2/5] can: raw: fix CAN FD frame transmissions over CAN XL devices
Date: Thu, 2 Feb 2023 14:47:56 +0100 [thread overview]
Message-ID: <bd2949e7-59d9-dc95-9010-3c304824d6dc@hartkopp.net> (raw)
In-Reply-To: <20230202131021.4xffrriiggebuzqf@pengutronix.de>
On 02.02.23 14:10, Marc Kleine-Budde wrote:
> On 02.02.2023 13:43:07, Oliver Hartkopp wrote:
>> you asked me to introduce a new variable instead of rolling back the
>> ro->fd_frames setting in setsockopt.
>>
>> I just wondered why you didn't pick the V4 patch then:
>
> Doh - that was not intentional!
>
No problem ;-)
>> https://lore.kernel.org/linux-can/20230131112657.59247-1-socketcan@hartkopp.net/T/#u
>>
>> It has no functional drawback but I was able to add an error return code in
>> V4. I just wanted to know.
>
> Please send a follow up patch against net-next/main once the net/main
> has been merged in net-next/main.
>
Ok, will do!
Thanks!
Oliver
next prev parent reply other threads:[~2023-02-02 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:41 [PATCH net 0/5] pull-request: can 2023-02-02 Marc Kleine-Budde
2023-02-02 9:41 ` [PATCH net 1/5] can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate Marc Kleine-Budde
2023-02-02 20:00 ` patchwork-bot+netdevbpf
2023-02-02 9:41 ` [PATCH net 2/5] can: raw: fix CAN FD frame transmissions over CAN XL devices Marc Kleine-Budde
2023-02-02 12:43 ` Oliver Hartkopp
2023-02-02 13:10 ` Marc Kleine-Budde
2023-02-02 13:47 ` Oliver Hartkopp [this message]
2023-02-03 9:12 ` Oliver Hartkopp
2023-02-02 9:41 ` [PATCH net 3/5] can: isotp: handle wait_event_interruptible() return values Marc Kleine-Budde
2023-02-02 9:41 ` [PATCH net 4/5] can: isotp: split tx timer into transmission and timeout Marc Kleine-Budde
2023-02-02 9:41 ` [PATCH net 5/5] can: mcp251xfd: mcp251xfd_ring_set_ringparam(): assign missing tx_obj_num_coalesce_irq 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=bd2949e7-59d9-dc95-9010-3c304824d6dc@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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.