All of lore.kernel.org
 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/7] pull-request: can 2023-05-18
Date: Thu, 18 May 2023 09:32:34 +0200	[thread overview]
Message-ID: <20230518073241.1110453-1-mkl@pengutronix.de> (raw)

Hello netdev-team,

this is a pull request of 7 patches for net/master.

The first 6 patches are by Jimmy Assarsson and fix several bugs in the
kvaser_pciefd driver.

The latest patch is from me and reverts a change in stm32f746.dtsi
that causes build errors due to a missing dependent patch.

regards,
Marc

---

The following changes since commit 6ad85ed0ebf7ece0f376950a6b3b3c6048093d35:

  Merge tag 'ipsec-2023-05-16' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec (2023-05-16 20:52:35 -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.4-20230518

for you to fetch changes up to 36a6418bb125944838b91a33eddca4064a5eb610:

  Revert "ARM: dts: stm32: add CAN support on stm32f746" (2023-05-17 20:20:12 +0200)

----------------------------------------------------------------
linux-can-fixes-for-6.4-20230518

----------------------------------------------------------------
Jimmy Assarsson (6):
      can: kvaser_pciefd: Set CAN_STATE_STOPPED in kvaser_pciefd_stop()
      can: kvaser_pciefd: Clear listen-only bit if not explicitly requested
      can: kvaser_pciefd: Call request_irq() before enabling interrupts
      can: kvaser_pciefd: Empty SRB buffer in probe
      can: kvaser_pciefd: Do not send EFLUSH command on TFD interrupt
      can: kvaser_pciefd: Disable interrupts in probe error path

Marc Kleine-Budde (2):
      Merge patch series "can: kvaser_pciefd: Bug fixes"
      Revert "ARM: dts: stm32: add CAN support on stm32f746"

 arch/arm/boot/dts/stm32f746.dtsi | 47 ------------------------------------
 drivers/net/can/kvaser_pciefd.c  | 51 +++++++++++++++++++++++-----------------
 2 files changed, 29 insertions(+), 69 deletions(-)



             reply	other threads:[~2023-05-18  7:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  7:32 Marc Kleine-Budde [this message]
2023-05-18  7:32 ` [PATCH net 1/7] can: kvaser_pciefd: Set CAN_STATE_STOPPED in kvaser_pciefd_stop() Marc Kleine-Budde
2023-05-18  9:50   ` patchwork-bot+netdevbpf
2023-05-18  7:32 ` [PATCH net 2/7] can: kvaser_pciefd: Clear listen-only bit if not explicitly requested Marc Kleine-Budde
2023-05-18  7:32 ` [PATCH net 3/7] can: kvaser_pciefd: Call request_irq() before enabling interrupts Marc Kleine-Budde
2023-05-18  7:32 ` [PATCH net 4/7] can: kvaser_pciefd: Empty SRB buffer in probe Marc Kleine-Budde
2023-05-18  7:32 ` [PATCH net 5/7] can: kvaser_pciefd: Do not send EFLUSH command on TFD interrupt Marc Kleine-Budde
2023-05-18  7:32 ` [PATCH net 6/7] can: kvaser_pciefd: Disable interrupts in probe error path Marc Kleine-Budde
2023-05-18  7:32 ` [PATCH net 7/7] Revert "ARM: dts: stm32: add CAN support on stm32f746" 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=20230518073241.1110453-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 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.