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 2024-03-20
Date: Wed, 20 Mar 2024 11:50:25 +0100	[thread overview]
Message-ID: <20240320112144.582741-1-mkl@pengutronix.de> (raw)

Hello netdev-team,

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

Martin Jocić contributes a fix for the kvaser_pciefd driver, so that
up to 8 channels on the Xilinx-based adapters can be used. This issue
has been introduced in net-next for v6.9.

regards,
Marc

---

The following changes since commit e54e09c05c00120cbe817bdb037088035be4bd79:

  net: remove {revc,send}msg_copy_msghdr() from exports (2024-03-14 16:48:53 -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.9-20240319

for you to fetch changes up to af1752ecdc9c665b72fbe2cef9035a6cba34b473:

  can: kvaser_pciefd: Add additional Xilinx interrupts (2024-03-19 15:26:01 +0100)

----------------------------------------------------------------
linux-can-fixes-for-6.9-20240319

----------------------------------------------------------------
Martin Jocić (1):
      can: kvaser_pciefd: Add additional Xilinx interrupts

 drivers/net/can/kvaser_pciefd.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


             reply	other threads:[~2024-03-20 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 10:50 Marc Kleine-Budde [this message]
2024-03-20 10:50 ` [PATCH net] can: kvaser_pciefd: Add additional Xilinx interrupts Marc Kleine-Budde
2024-03-21 12:20   ` 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=20240320112144.582741-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).