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] [thread-next>] [day] [month] [year] [list]
Message-ID: <680b91c0-0fae-4230-9fa1-da988cb82e65@gmail.com>
Date: Thu, 10 Jul 2025 00:22:02 -0400
From: David Hunter <david.hunter.linux@...il.com>
To: Hanne-Lotta Mäenpää <hannelotta@...il.com>,
 mchehab@...nel.org
Cc: linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-kernel-mentees@...ts.linux.dev, skhan@...uxfoundation.org
Subject: Re: [PATCH v4] media: Documentation: Improve grammar in DVB API

On 7/8/25 11:52, Hanne-Lotta Mäenpää wrote:
> Fix typos and punctuation and improve grammar in documentation.
> 
> Signed-off-by: Hanne-Lotta Mäenpää <hannelotta@...il.com>

Overall, good work. Here is a suggestion for future patch series:

Subsequent versions of patch series should be posted as replies in the same thread. Currently, each version is its own independent thread, which makes it hard to track changes. This link has the documentation for the proper way to handle subsequent patches:

https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html

The relevant part starts at "To that end, send them as replies to either..."

Another good practice is to have the previous versions' links from "lore.kernel.org" directly in the change log. 

Thanks, 
David Hunter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ