From: Jakub Kicinski <kuba@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH net 0/n] pull-request: can 2025-05-21
Date: Wed, 21 May 2025 20:41:14 -0700 [thread overview]
Message-ID: <20250521204114.1d131ff9@kernel.org> (raw)
In-Reply-To: <20250521082239.341080-2-mkl@pengutronix.de>
On Wed, 21 May 2025 10:14:24 +0200 Marc Kleine-Budde wrote:
> Subject: [PATCH net 0/n] pull-request: can 2025-05-21
Looks like the 0/n confused patchwork and it couldn't do our build
testing. Given that we're targeting the final release I'd rather
not risk merging this without a full run thru our builds.
Could you respin? Not sure it will make tomorrow's PR but then again
I don't think anything here is super critical for 6.15 final?
Sorry for not noticing earlier.
next prev parent reply other threads:[~2025-05-22 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 8:14 [PATCH net 0/n] pull-request: can 2025-05-21 Marc Kleine-Budde
2025-05-21 8:14 ` [PATCH net 1/4] can: kvaser_pciefd: Force IRQ edge in case of nested IRQ Marc Kleine-Budde
2025-05-21 8:14 ` [PATCH net 2/4] can: kvaser_pciefd: Fix echo_skb race Marc Kleine-Budde
2025-05-21 8:14 ` [PATCH net 3/4] can: kvaser_pciefd: Continue parsing DMA buf after dropped RX Marc Kleine-Budde
2025-05-21 8:14 ` [PATCH net 4/4] can: slcan: allow reception of short error messages Marc Kleine-Budde
2025-05-22 3:41 ` Jakub Kicinski [this message]
2025-05-22 8:28 ` [PATCH net 0/n] pull-request: can 2025-05-21 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=20250521204114.1d131ff9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.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 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.