From: Jakub Kicinski <kuba@kernel.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Robin van der Gracht <robin@protonic.nl>,
Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6 6/6] can: gw: use can_gw_hops instead of sk_buff::csum_start
Date: Fri, 30 Jan 2026 17:41:10 -0800 [thread overview]
Message-ID: <20260130174110.1c552bf7@kernel.org> (raw)
In-Reply-To: <93d61e1c-5cdf-498e-8699-43e57cbb221b@hartkopp.net>
On Fri, 30 Jan 2026 10:29:37 +0100 Oliver Hartkopp wrote:
> I'll wait for a respin until tomorrow.
FTR 24h means 24h, you seem to be reposting "tomorrow"
before a full day has passed.
prev parent reply other threads:[~2026-01-31 1:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 8:41 [PATCH net-next v6 0/6] move CAN skb headroom content to skb extensions Oliver Hartkopp via B4 Relay
2026-01-30 8:41 ` [PATCH net-next v6 1/6] can: use skb hash instead of private variable in headroom Oliver Hartkopp via B4 Relay
2026-01-30 8:41 ` [PATCH net-next v6 2/6] can: add CAN skb extension infrastructure Oliver Hartkopp via B4 Relay
2026-01-30 8:41 ` [PATCH net-next v6 3/6] can: move ifindex to CAN skb extensions Oliver Hartkopp via B4 Relay
2026-01-30 8:41 ` [PATCH net-next v6 4/6] can: move frame_len " Oliver Hartkopp via B4 Relay
2026-01-30 8:41 ` [PATCH net-next v6 5/6] can: remove private CAN skb headroom infrastructure Oliver Hartkopp via B4 Relay
2026-01-30 8:42 ` [PATCH net-next v6 6/6] can: gw: use can_gw_hops instead of sk_buff::csum_start Oliver Hartkopp via B4 Relay
2026-01-30 9:29 ` Oliver Hartkopp
2026-01-31 1:41 ` Jakub Kicinski [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=20260130174110.1c552bf7@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
/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