linux-kernel - Re: [PATCH RESEND 1/1] Revert "spi/doc: spi_master

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] [day] [month] [year] [list]

Message-ID: <20150906000433.GQ5313@sirena.org.uk>
Date:	Sun, 6 Sep 2015 01:04:33 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Alexey Klimov <alexey.klimov@...aro.org>
Cc:	linux@...ck-us.net, linux-spi@...r.kernel.org,
	linux-kernel@...r.kernel.org, djkurtz@...omium.org,
	klimov.linux@...il.com,
	Uwe Kleine-Koenig <u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH RESEND 1/1] Revert "spi/doc: spi_master_put must be
 followed up by kfree"

On Sun, Sep 06, 2015 at 01:46:54AM +0300, Alexey Klimov wrote:
> From: Guenter Roeck <linux@...ck-us.net>
> 
> Actually, spi_master_put() after spi_alloc_master() must _not_ be followed

Please use subject lines matching the style for the subsystem and please
don't put noise like RESEND in the subject line, especially if the patch
isn't actually being resent.  Both these things make it easier to scan
incoming mail for relevant and important patches.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)