netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	linux-can@vger.kernel.org, kernel@pengutronix.de,
	kuniyu@amazon.com,
	syzbot+0532ac7a06fb1a03187e@syzkaller.appspotmail.com,
	mailhol.vincent@wanadoo.fr
Subject: Re: [PATCH net 1/5] can: bcm: Clear bo->bcm_proc_read after remove_proc_entry().
Date: Sat, 14 Sep 2024 04:30:30 +0000	[thread overview]
Message-ID: <172628823052.2458848.2139057553371045622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240912075804.2825408-2-mkl@pengutronix.de>

Hello:

This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:

On Thu, 12 Sep 2024 09:50:50 +0200 you wrote:
> From: Kuniyuki Iwashima <kuniyu@amazon.com>
> 
> syzbot reported a warning in bcm_release(). [0]
> 
> The blamed change fixed another warning that is triggered when
> connect() is issued again for a socket whose connect()ed device has
> been unregistered.
> 
> [...]

Here is the summary with links:
  - [net,1/5] can: bcm: Clear bo->bcm_proc_read after remove_proc_entry().
    https://git.kernel.org/netdev/net/c/94b0818fa635
  - [net,2/5] can: esd_usb: Remove CAN_CTRLMODE_3_SAMPLES for CAN-USB/3-FD
    https://git.kernel.org/netdev/net/c/75b318954057
  - [net,3/5] can: kvaser_pciefd: Enable 64-bit DMA addressing
    https://git.kernel.org/netdev/net/c/d0fa06408ccf
  - [net,5/5] can: m_can: m_can_close(): stop clocks after device has been shut down
    https://git.kernel.org/netdev/net/c/2c09b50efcad
  - [net-next,4/5] can: rockchip_canfd: rkcanfd_timestamp_init(): rework delay calculation
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-09-14  4:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  7:50 [PATCH net 0/5] pull-request: can 2024-09-12 Marc Kleine-Budde
2024-09-12  7:50 ` [PATCH net 1/5] can: bcm: Clear bo->bcm_proc_read after remove_proc_entry() Marc Kleine-Budde
2024-09-14  4:30   ` patchwork-bot+netdevbpf [this message]
2024-09-14  4:50   ` patchwork-bot+netdevbpf
2024-09-12  7:50 ` [PATCH net 2/5] can: esd_usb: Remove CAN_CTRLMODE_3_SAMPLES for CAN-USB/3-FD Marc Kleine-Budde
2024-09-12  7:50 ` [PATCH net 3/5] can: kvaser_pciefd: Enable 64-bit DMA addressing Marc Kleine-Budde
2024-09-12  7:50 ` [PATCH net 4/5] can: m_can: enable NAPI before enabling interrupts Marc Kleine-Budde
2024-09-14  4:30   ` patchwork-bot+netdevbpf
2024-09-12  7:50 ` [PATCH net 5/5] can: m_can: m_can_close(): stop clocks after device has been shut down 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=172628823052.2458848.2139057553371045622.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+0532ac7a06fb1a03187e@syzkaller.appspotmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).