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 2022-03-31
Date: Thu, 31 Mar 2022 08:51:18 -0700 [thread overview]
Message-ID: <20220331085118.3a118acb@kernel.org> (raw)
In-Reply-To: <20220331154549.wqtxsepujwwap5wg@pengutronix.de>
On Thu, 31 Mar 2022 17:45:49 +0200 Marc Kleine-Budde wrote:
> > I think patchwork did not like the "0/n" in the subject :(
>
> Should I resend (with a fixed subject)?
I should have clarified that :) It's okay - I had to build test
manually before sending the PR to Linus, anyway. Looks clean.
next prev parent reply other threads:[~2022-03-31 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 8:46 [PATCH net 0/n] pull-request: can 2022-03-31 Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 1/8] can: isotp: restore accidentally removed MSG_PEEK feature Marc Kleine-Budde
2022-03-31 15:50 ` patchwork-bot+netdevbpf
2022-03-31 8:46 ` [PATCH net 2/8] can: mcp251xfd: mcp251xfd_register_get_dev_id(): fix return of error value Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 3/8] can: m_can: m_can_tx_handler(): fix use after free of skb Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 4/8] can: ems_usb: ems_usb_start_xmit(): fix double dev_kfree_skb() in error path Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 5/8] can: usb_8dev: usb_8dev_start_xmit(): " Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 6/8] can: mcba_usb: mcba_usb_start_xmit(): fix double dev_kfree_skb " Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 7/8] can: mcba_usb: properly check endpoint type Marc Kleine-Budde
2022-03-31 8:46 ` [PATCH net 8/8] can: gs_usb: gs_make_candev(): fix memory leak for devices with extended bit timing configuration Marc Kleine-Budde
2022-03-31 15:42 ` [PATCH net 0/n] pull-request: can 2022-03-31 Jakub Kicinski
2022-03-31 15:45 ` Marc Kleine-Budde
2022-03-31 15:51 ` Jakub Kicinski [this message]
2022-03-31 15:50 ` patchwork-bot+netdevbpf
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=20220331085118.3a118acb@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.