linux-kernel - Re: [PATCH] qeth: don't rely on signedness of char

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: <20151207134744.GB2716@osiris>
Date:	Mon, 7 Dec 2015 14:47:44 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Ursula Braun <ubraun@...ux.vnet.ibm.com>
Cc:	Rasmus Villemoes <linux@...musvillemoes.dk>,
	Ursula Braun <ursula.braun@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] qeth: don't rely on signedness of char

On Mon, Dec 07, 2015 at 01:02:35PM +0100, Ursula Braun wrote:
> Rasmus,
> 
> I do not see a need for your first patch proposal. Our code works fine
> in our environment.
> 
> But I will pickup your second part to remove the explicit setting of the
> 0-termination. Thanks!
> 
> Regards, Ursula

Hi Uschi,

das untenstehende habe ich schon diverse male geschrieben, um zu
verhindern, dass "wir" uns mit einfach vermeidbaren Dingen auf externen
Mailinglisten unbeliebt machen:

Just a general comment and unrelated to this patch.
Please, when replying:

- don't top-post
- use interleaved style with an empty line after each quoted block
- trim your replies to only the relevant parts

See also: https://en.wikipedia.org/wiki/Posting_style

This should make your and everybody else's life easier when your are
participating on external mailing lists.

--
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/