From: "Ricardo B. Marliere" <ricardo@marliere.net>
To: Guillaume Nault <gnault@redhat.com>
Cc: Oliver Neukum <oneukum@suse.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Loic Poulain <loic.poulain@linaro.org>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Johannes Berg <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,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 04/12] net: vxlan: constify the struct device_type usage
Date: Mon, 19 Feb 2024 08:49:47 -0300 [thread overview]
Message-ID: <wcvz4nnmhiz5ktrr6mww5sjaxmr6fewjay3hjrlurlkeg3fcor@ntspq2qi2bfz> (raw)
In-Reply-To: <ZdM+4uKE83V2j4o8@debian>
Hi Guillaume,
On 19 Feb 12:43, Guillaume Nault wrote:
> On Sat, Feb 17, 2024 at 05:13:26PM -0300, Ricardo B. Marliere wrote:
> > Since commit aed65af1cc2f ("drivers: make device_type const"), the driver
> > core can properly handle constant struct device_type. Move the vxlan_type
> > variable to be a constant structure as well, placing it into read-only
> > memory which can not be modified at runtime.
>
> Reviewed-by: Guillaume Nault <gnault@redhat.com>
>
> Note: To help maintainers (and potentially reviewers) work please
> write in the subject prefix which tree you're targetting. For this
> series, it should be "[PATCH net-next xx/yy]".
Makes sense, will keep this in mind next time!
Thanks for reviewing,
- Ricardo.
next prev parent reply other threads:[~2024-02-19 11:49 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 [this message]
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 ` [PATCH 00/12] net: constify " 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=wcvz4nnmhiz5ktrr6mww5sjaxmr6fewjay3hjrlurlkeg3fcor@ntspq2qi2bfz \
--to=ricardo@marliere.net \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gnault@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=ryazanov.s.a@gmail.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 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 NNTP newsgroup(s).