linux-kernel - Re: [PATCH 1/3] drivers: usb: Fix block comments whose trailing */ was not on a separate line

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: <2023100133-exclusive-boss-edc4@gregkh>
Date:   Sun, 1 Oct 2023 08:06:06 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Jonathan Bergh <bergh.jonathan@...il.com>
Cc:     linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] drivers: usb: Fix block comments whose trailing */
 was not on a separate line

On Sat, Sep 30, 2023 at 10:36:46PM +0200, Jonathan Bergh wrote:
> Fixed various instances where block comments trailing */ where not on a
> separate line and should be.
> 
> Signed-off-by: Jonathan Bergh <bergh.jonathan@...il.com>
> ---
>  drivers/usb/atm/cxacru.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)

Your subject line for these patches is not correct, please fix up.

And the patches are not properly threaded, what happened in your email
client?

And finally, why make coding style changes outside of drivers/staging/?
Did you get the maintainer's approval to do so before taking the time?
Usually most maintainers do not want these so always ask before doing
so, or just stick with drivers/staging/ to learn how the process works
first please.

thanks,

greg k-h