Linux-Can 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,
	martin.jocic@kvaser.com
Subject: Re: [PATCH net] can: kvaser_pciefd: Add additional Xilinx interrupts
Date: Thu, 21 Mar 2024 12:20:26 +0000	[thread overview]
Message-ID: <171102362678.4643.10285446325586255117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240320112144.582741-2-mkl@pengutronix.de>

Hello:

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

On Wed, 20 Mar 2024 11:50:26 +0100 you wrote:
> From: Martin Jocić <martin.jocic@kvaser.com>
> 
> Since Xilinx-based adapters now support up to eight CAN channels, the
> TX interrupt mask array must have eight elements.
> 
> Signed-off-by: Martin Jocic <martin.jocic@kvaser.com>
> Link: https://lore.kernel.org/all/2ab3c0585c3baba272ede0487182a423a420134b.camel@kvaser.com
> Fixes: 9b221ba452aa ("can: kvaser_pciefd: Add support for Kvaser PCIe 8xCAN")
> [mkl: replace Link by Fixes tag]
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> 
> [...]

Here is the summary with links:
  - [net] can: kvaser_pciefd: Add additional Xilinx interrupts
    https://git.kernel.org/netdev/net/c/af1752ecdc9c

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



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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 10:50 [PATCH net 0/1] pull-request: can 2024-03-20 Marc Kleine-Budde
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 [this message]

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=171102362678.4643.10285446325586255117.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=martin.jocic@kvaser.com \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).