linux-kernel - Re: [PATCH] siox: don't create a thread without starting it

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: <20180629073858.5gwpfwqo2ccb4jaa@pengutronix.de>
Date:   Fri, 29 Jun 2018 09:38:58 +0200
From:   Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
To:     Greg Kroah-Hartman <gregkh@...e.de>
Cc:     Gavin Schenk <g.schenk@...elmann.de>, linux-kernel@...r.kernel.org,
        kernel@...gutronix.de, Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH] siox: don't create a thread without starting it

Hello Greg,

Cc -= Peter Zijlstra
Cc += Stephen Rothwell

On Thu, Jun 28, 2018 at 09:57:42AM +0200, Uwe Kleine-König wrote:
> Greg, you applied the initial patches creating drivers/siox. I assume
> you will continue to apply siox patches and tell if I should search a
> different path for these.

I put the two patches that I'd like to get in during the next merge
window into a branch in my repository:

	https://git.pengutronix.de/git/ukl/linux siox/next

I assume you wouldn't object to add this branch to linux-next?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |