From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751715AbdIMVpc (ORCPT <rfc822;w@1wt.eu>);
        Wed, 13 Sep 2017 17:45:32 -0400
Received: from mx2.suse.de ([195.135.220.15]:60124 "EHLO mx1.suse.de"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1751631AbdIMVot (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 13 Sep 2017 17:44:49 -0400
Date: Wed, 13 Sep 2017 23:44:23 +0200
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        Marcel Holtmann <marcel@holtmann.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        stable <stable@vger.kernel.org>, Gabriel C <nix.or.die@gmail.com>,
        Arend Van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH 4.13 20/27] Revert "firmware: add sanity check on
 shutdown/suspend"
Message-ID: <20170913214423.GV16216@wotan.suse.de>
References: <20170912165308.904472972@linuxfoundation.org>
 <20170912165310.407586301@linuxfoundation.org>
 <20170912172008.GF16216@wotan.suse.de>
 <20170913004758.GA21439@kroah.com>
 <CA+55aFw9S7f6eawrH6B5M-sTca9TT2sjzBU14xijBCeSpmCkHA@mail.gmail.com>
 <20170913183809.GN16216@wotan.suse.de>
 <CA+55aFxU_RqskECWOCSY-3jCU-aYxD_hO08HJvhZ3OC+22_jJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFxU_RqskECWOCSY-3jCU-aYxD_hO08HJvhZ3OC+22_jJw@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Sep 13, 2017 at 12:30:44PM -0700, Linus Torvalds wrote:
> Yes, the movement of the locking might need to be reverted too - but
> only if it actually shows problems.

This speeds up the cleanup of that crap UMH code so I'm happy to
wait to hear if just the move the UMH lock it creates an issue.

I suspect it wont.

  Luis