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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241130140659.4518f4a3@kernel.org>
Date: Sat, 30 Nov 2024 14:06:59 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jesse Van Gavere <jesseevg@...il.com>
Cc: netdev@...r.kernel.org, woojung.huh@...rochip.com,
 UNGLinuxDriver@...rochip.com, andrew@...n.ch, olteanv@...il.com, Jesse Van
 Gavere <jesse.vangavere@...oteq.com>
Subject: Re: [PATCH] net: dsa: microchip: KSZ9896 register regmap alignment
 to 32 bit boundaries

On Wed, 27 Nov 2024 23:11:29 +0100 Jesse Van Gavere wrote:
> Commit (SHA1: 8d7ae22ae9f8c8a4407f8e993df64440bdbd0cee) fixed this issue
> for the KSZ9477 by adjusting the regmap ranges.

The correct format for referring to other commits in Linux kernel is:
 %h (\"%s\")
IOW:

 Commit 8d7ae22ae9f8 ("net: dsa: microchip: KSZ9477 register regmap
 alignment to 32 bit boundaries") fixed this issue...

> The same issue presents itself on the KSZ9896 regs and is fixed with 
> the same regmap range modification.

Could you explain the impact? What will not work / break without this
change? Please add a Fixes tag indicating where buggy code was added
to make sure backporters know how far to backport.
-- 
pw-bot: cr

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ