public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Ricardo B. Marliere <ricardo@marliere•net>
Cc: oneukum@suse•com, davem@davemloft•net, edumazet@google•com,
	kuba@kernel•org, pabeni@redhat•com, andrew@lunn•ch,
	f.fainelli@gmail•com, olteanv@gmail•com, roopa@nvidia•com,
	razor@blackwall•org, loic.poulain@linaro•org,
	ryazanov.s.a@gmail•com, johannes@sipsolutions•net,
	netdev@vger•kernel.org, linux-usb@vger•kernel.org,
	linux-kernel@vger•kernel.org, bridge@lists•linux.dev,
	linux-ppp@vger•kernel.org, gregkh@linuxfoundation•org
Subject: Re: [PATCH 00/12] net: constify struct device_type usage
Date: Wed, 21 Feb 2024 09:50:28 +0000	[thread overview]
Message-ID: <170850902848.18277.9807669869009277382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240217-device_cleanup-net-v1-0-1eb31fb689f7@marliere.net>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:

On Sat, 17 Feb 2024 17:13:22 -0300 you wrote:
> This is a simple and straight forward cleanup series that makes all device
> types in the net subsystem constants. This has been possible since 2011 [1]
> but not all occurrences were cleaned. I have been sweeping the tree to fix
> them all.
> 
> I was not sure if I should send these squashed, but there are quite a few
> changes so I decided to send them separately. Please let me know if that is
> not desirable.
> 
> [...]

Here is the summary with links:
  - [01/12] net: usbnet: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/3ce7caee3af0
  - [02/12] net: dsa: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/7e0acba3b49e
  - [03/12] net: bridge: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/bbc7e4cc21a4
  - [04/12] net: vxlan: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/c7170e7672e5
  - [05/12] net: ppp: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/908ada0da6d4
  - [06/12] net: geneve: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/e443f3acbc6d
  - [07/12] net: hsr: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/0072b2c1ffd0
  - [08/12] net: l2tp: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/43820fd1ddb5
  - [09/12] net: vlan: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/7ae9d3423f1d
  - [10/12] net: netdevsim: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/52042e092ba9
  - [11/12] net: wwan: core: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/7eccf41b3bac
  - [12/12] net: hso: constify the struct device_type usage
    https://git.kernel.org/netdev/net-next/c/55fad9c4a3c4

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



      parent reply	other threads:[~2024-02-21  9:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 20:13 [PATCH 00/12] net: constify struct device_type usage Ricardo B. Marliere
2024-02-17 20:13 ` [PATCH 01/12] net: usbnet: constify the " Ricardo B. Marliere
2024-02-20 11:18   ` Simon Horman
2024-02-17 20:13 ` [PATCH 02/12] net: dsa: " Ricardo B. Marliere
2024-02-18 21:46   ` Florian Fainelli
2024-02-17 20:13 ` [PATCH 03/12] net: bridge: " Ricardo B. Marliere
2024-02-20 11:20   ` Simon Horman
2024-02-17 20:13 ` [PATCH 04/12] net: vxlan: " Ricardo B. Marliere
2024-02-19 11:43   ` Guillaume Nault
2024-02-19 11:49     ` Ricardo B. Marliere
2024-02-17 20:13 ` [PATCH 05/12] net: ppp: " Ricardo B. Marliere
2024-02-19 11:44   ` Guillaume Nault
2024-02-17 20:13 ` [PATCH 06/12] net: geneve: " Ricardo B. Marliere
2024-02-19 11:45   ` Guillaume Nault
2024-02-17 20:13 ` [PATCH 07/12] net: hsr: " Ricardo B. Marliere
2024-02-20 11:21   ` Simon Horman
2024-02-17 20:13 ` [PATCH 08/12] net: l2tp: " Ricardo B. Marliere
2024-02-19 11:46   ` Guillaume Nault
2024-02-17 20:13 ` [PATCH 09/12] net: vlan: " Ricardo B. Marliere
2024-02-20 11:21   ` Simon Horman
2024-02-17 20:13 ` [PATCH 10/12] net: netdevsim: " Ricardo B. Marliere
2024-02-20 11:22   ` Simon Horman
2024-02-17 20:13 ` [PATCH 11/12] net: wwan: core: " Ricardo B. Marliere
2024-02-20 11:22   ` Simon Horman
2024-02-21  0:07   ` Sergey Ryazanov
2024-02-17 20:13 ` [PATCH 12/12] net: hso: " Ricardo B. Marliere
2024-02-20 11:22   ` Simon Horman
2024-02-21  9:50 ` 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=170850902848.18277.9807669869009277382.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=andrew@lunn$(echo .)ch \
    --cc=bridge@lists$(echo .)linux.dev \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-ppp@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=loic.poulain@linaro$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=olteanv@gmail$(echo .)com \
    --cc=oneukum@suse$(echo .)com \
    --cc=pabeni@redhat$(echo .)com \
    --cc=razor@blackwall$(echo .)org \
    --cc=ricardo@marliere$(echo .)net \
    --cc=roopa@nvidia$(echo .)com \
    --cc=ryazanov.s.a@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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