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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8fea55a9-54f8-405b-9844-ee67b5e43ba3@gmail.com>
Date: Mon, 6 Oct 2025 21:16:26 -0400
From: David Hunter <david.hunter.linux@...il.com>
To: vivekyadav1207731111@...il.com, johan@...nel.org,
 gregkh@...uxfoundation.org
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
 skhan@...uxfoundation.org, linux-kernel-mentees@...ts.linux.dev
Subject: Re: [PATCH] usb: serial: fix: trainling statements `break` should be
 on next line

On 10/4/25 04:01, vivekyadav1207731111@...il.com wrote:

> +		case 300:
> +		case 600:
> +		case 1200:
> +		case 2400:
> +		case 4800:
> +		case 9600:
> +		case 19200:
> +		case 38400:
> +		case 57600:
> +		case 115200:
> +			break;

It is generally considered best practice to use the breaks after each
case. Here is a good article on this:

https://lwn.net/Articles/794944/


Also, same here. no top-posting:

https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ