| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20230718183315.27c0cd27@kernel.org>
Date: Tue, 18 Jul 2023 18:33:15 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: netdev@...r.kernel.org, davem@...emloft.net, linux-can@...r.kernel.org,
kernel@...gutronix.de, Jimmy Assarsson <extja@...ser.com>, Martin Jocic
<majoc@...ser.com>
Subject: Re: [PATCH net-next 7/8] can: kvaser_pciefd: Move hardware specific
constants and functions into a driver_data struct
On Mon, 17 Jul 2023 20:22:28 +0200 Marc Kleine-Budde wrote:
> +const struct kvaser_pciefd_address_offset kvaser_pciefd_altera_address_offset = {
> +const struct kvaser_pciefd_irq_mask kvaser_pciefd_altera_irq_mask = {
> +const struct kvaser_pciefd_dev_ops kvaser_pciefd_altera_dev_ops = {
> +const struct kvaser_pciefd_driver_data kvaser_pciefd_altera_driver_data = {
sparse points out the structs in this and subsequent patch should
be static. Would you be able to queue a quick fix on top and resend,
or should we pull as is?
Powered by blists - more mailing lists