All of lore.kernel.org
 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, jm@ti.com,
	tony@atomide.com, conor.dooley@microchip.com,
	krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH net-next 1/8] dt-bindings: net: can: Remove interrupt properties for MCAN
Date: Wed, 19 Jul 2023 22:10:22 +0000	[thread overview]
Message-ID: <168980462277.30545.412966680711424216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230719072348.525039-2-mkl@pengutronix.de>

Hello:

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

On Wed, 19 Jul 2023 09:23:41 +0200 you wrote:
> From: Judith Mendez <jm@ti.com>
> 
> On AM62x SoC, MCANs on MCU domain do not have hardware interrupt
> routed to A53 Linux, instead they will use software interrupt by
> timer polling.
> 
> To enable timer polling method, interrupts should be
> optional so remove interrupts property from required section and
> add an example for MCAN node with timer polling enabled.
> 
> [...]

Here is the summary with links:
  - [net-next,1/8] dt-bindings: net: can: Remove interrupt properties for MCAN
    https://git.kernel.org/netdev/net-next/c/bb410c03b999
  - [net-next,2/8] can: m_can: Add hrtimer to generate software interrupt
    https://git.kernel.org/netdev/net-next/c/b382380c0d2d
  - [net-next,3/8] dt-bindings: can: xilinx_can: Add reset description
    https://git.kernel.org/netdev/net-next/c/62bd0232d745
  - [net-next,4/8] can: xilinx_can: Add support for controller reset
    https://git.kernel.org/netdev/net-next/c/25000fc785b4
  - [net-next,5/8] can: Explicitly include correct DT includes
    https://git.kernel.org/netdev/net-next/c/22d8e8d6338d
  - [net-next,6/8] can: kvaser_pciefd: Move hardware specific constants and functions into a driver_data struct
    https://git.kernel.org/netdev/net-next/c/c2ad812956ae
  - [net-next,7/8] can: kvaser_pciefd: Add support for new Kvaser pciefd devices
    https://git.kernel.org/netdev/net-next/c/f33ad6776b2f
  - [net-next,8/8] can: ucan: Remove repeated word
    https://git.kernel.org/netdev/net-next/c/03df47c1bb39

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



  reply	other threads:[~2023-07-19 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  7:23 [PATCH net-next 0/8] pull-request: can-next 2023-07-19 Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 1/8] dt-bindings: net: can: Remove interrupt properties for MCAN Marc Kleine-Budde
2023-07-19 22:10   ` patchwork-bot+netdevbpf [this message]
2023-07-19  7:23 ` [PATCH net-next 2/8] can: m_can: Add hrtimer to generate software interrupt Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 3/8] dt-bindings: can: xilinx_can: Add reset description Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 4/8] can: xilinx_can: Add support for controller reset Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 5/8] can: Explicitly include correct DT includes Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 6/8] can: kvaser_pciefd: Move hardware specific constants and functions into a driver_data struct Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 7/8] can: kvaser_pciefd: Add support for new Kvaser pciefd devices Marc Kleine-Budde
2023-07-19  7:23 ` [PATCH net-next 8/8] can: ucan: Remove repeated word Marc Kleine-Budde
  -- strict thread matches above, loose matches on Subject: below --
2023-07-17 18:22 [PATCH net-next 0/8] pull-request: can-next 2023-07-17 Marc Kleine-Budde
2023-07-17 18:22 ` [PATCH net-next 1/8] dt-bindings: net: can: Remove interrupt properties for MCAN Marc Kleine-Budde
2023-07-19  2:10   ` 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=168980462277.30545.412966680711424216.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=jm@ti.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=tony@atomide.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 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.