netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
	kernel@pengutronix.de
Subject: [PATCH net 0/1] pull-request: can 2025-07-11
Date: Fri, 11 Jul 2025 12:22:27 +0200	[thread overview]
Message-ID: <20250711102451.2828802-1-mkl@pengutronix.de> (raw)

Hello netdev-team,

this is a pull request of 1 patch for net/main.

Sean Nyekjaer's patch targets the m_can driver and demotes the "msg
lost in rx" message to debug level to prevent flooding the kernel log
with error messages.

regards,
Marc

---

The following changes since commit 47c84997c686b4d43b225521b732492552b84758:

  selftests: net: lib: fix shift count out of range (2025-07-10 18:11:52 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-6.16-20250711

for you to fetch changes up to 58805e9cbc6f6a28f35d90e740956e983a0e036e:

  can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (2025-07-11 12:18:58 +0200)

----------------------------------------------------------------
linux-can-fixes-for-6.16-20250711

----------------------------------------------------------------
Sean Nyekjaer (1):
      can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level

 drivers/net/can/m_can/m_can.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


             reply	other threads:[~2025-07-11 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 10:22 Marc Kleine-Budde [this message]
2025-07-11 10:22 ` [PATCH net] can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level Marc Kleine-Budde
2025-07-11 14:30   ` 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=20250711102451.2828802-1-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --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 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).