linux-kernel - Re: [PATCH]: MUX n_gsm debug print improvements

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]

Date:	Mon, 29 Jun 2015 09:02:38 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Gwenn Bourrée <gwenn.bourree@...el.com>
Cc:	jslaby@...e.cz, linux-api@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: MUX n_gsm debug print improvements

On Mon, Jun 29, 2015 at 05:54:58PM +0200, Gwenn Bourrée wrote:
> 
> Dear kernel tty maintainers,
> 
> Please review the following patch:
> 
> From 0ac5da0a4653f43ce4b0761a2be8073185c549bb Mon Sep 17 00:00:00 2001
> From: Gwenn Bourree <gwenn.bourree@...el.com>
> Date: Mon, 29 Jun 2015 16:09:06 +0200
> Subject: [PATCH] Add Debug define
> 
> Improve the debug print out and make be clearest
> 
> Signed-off-by: Gwenn Bourree <gwenn.bourree@...el.com>
> Signed-off-by: Mustapha Ben Zoubeir <mustaphax.ben.zoubeir@...el.com>
> Signed-off-by: Nicolas LOUIS <nicolasx.louis@...el.com>
> Reviewed-by: Ravindran, Arun <arun.ravindran@...el.com

Any reason you didn't cc the linux-serial mailing list?  And linux-api
only cares about external api changes, which I don't think you did here.

Also, what's with the odd format, I would have to hand-edit this in
order to apply it properly.  Please fix it up and send it without the
"Dear..." lines, that's not needed at all, nor is the "From" lines.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/