All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: mailhol.vincent@wanadoo.fr, kuba@kernel.org, mkl@pengutronix.de,
	davem@davemloft.net, biju.das.jz@bp.renesas.com,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] can: rcar_canfd: Describe channel-specific FD registers using C struct
Date: Sat, 21 Jun 2025 15:00:21 +0000	[thread overview]
Message-ID: <175051802124.1877807.84993120749211212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <292b75b3bc8dd95f805f0223f606737071c8cf86.1750327217.git.geert+renesas@glider.be>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 19 Jun 2025 12:13:17 +0200 you wrote:
> The rcar_canfd_f_*() inline functions to obtain channel-specific CAN-FD
> register offsets really describe a memory layout.  Hence replace them by
> a C structure, to simplify the code, and reduce kernel size.
> 
> This also gets rid of warnings about unused rcar_canfd_f_*() inline
> functions, which are reported by recent versions of clang.
> 
> [...]

Here is the summary with links:
  - can: rcar_canfd: Describe channel-specific FD registers using C struct
    https://git.kernel.org/netdev/net-next/c/ab2aa5453bb8

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



      parent reply	other threads:[~2025-06-21 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 10:13 [PATCH] can: rcar_canfd: Describe channel-specific FD registers using C struct Geert Uytterhoeven
2025-06-19 11:12 ` Vincent Mailhol
2025-06-19 11:56   ` Geert Uytterhoeven
2025-06-19 14:41   ` Jakub Kicinski
2025-06-21 15:00 ` 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=175051802124.1877807.84993120749211212.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=geert+renesas@glider.be \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --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 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.