From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3BD99C46467 for ; Wed, 14 Dec 2022 14:37:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238671AbiLNOhv (ORCPT ); Wed, 14 Dec 2022 09:37:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238664AbiLNOht (ORCPT ); Wed, 14 Dec 2022 09:37:49 -0500 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D48E23BEA for ; Wed, 14 Dec 2022 06:37:48 -0800 (PST) Received: by mail-wm1-x329.google.com with SMTP id b24-20020a05600c4a9800b003d21efdd61dso9373530wmp.3 for ; Wed, 14 Dec 2022 06:37:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=t2XJM1BjNmCMgH/G0fBVGH4bStfXGZIoDxsB1bZq0mQ=; b=ccHeRQ7iudNH2CTygNE/tMhdIuxXDlLm7TaDUgXtcDtEq/qU2RsnoLkMQXd94QSah8 E9CUUxjqmUom/K/eo8plBi57n4rLqcKrmXbO3TfQ2EFCxJwfefp28EYigB9F7SGfgQ8z vqRdz3zqmB0LHo5LFjLB3HlxFMfaP31GrVQfy/hWk5gUCG+EiVqdsH6nX2GMksTj/XYA TIX4Uy+KAiZD+JTwQcNTXbGbrw74ZHG1xKhGfVYHBN9Bwxlam/5hYmHW2zcT2xTWfy6v yH61Fhy/6houjn8pI3EISFnmraVKFUx/lR3RLrsyKBcCeibkuXJqCkRRRWrQkGYzsQj8 ZARA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=t2XJM1BjNmCMgH/G0fBVGH4bStfXGZIoDxsB1bZq0mQ=; b=Tlr6a7HxN5HGVajyzBx7gvzbstUvjnxOp3SR0WY2XLfOZgxlFql51gY05yq8nPK5yN iarSoWcwfhXAFp9yPpc6cVTjoayESmW07sPeK8Wohu1yp/FAyU8o0l9jFoQTAkSVUk/Y mnee0ZcHrQ0SkXF47zbK6rirfVvGBC1UAQskHGMnUpugFruCaOo2a89nuPUy+3jsEVms vycQv6b+PuCNJf2PiP8IGCRJn00HA06EHXbjK4XKWsKVYX/4XgoMTqJqxx6ivfnYWk4J DeNEBRxRHwvUn+XFr1GWY12rr05XVDN1MPj806eYSgcifw+jhaRWaBmnW0tsbvxz8ZKQ chfQ== X-Gm-Message-State: ANoB5pnonr/DHDod2JPCFAPk98/K9h/AAt1N96f7LC7mVG2BHAuuzeVR Pqh/vTKw3bijkVTYZvtgZEkfJQ== X-Google-Smtp-Source: AA0mqf6rGNM3iD66PMCSzvUVjsWDd3eVZpyPQ8IakTm/dMjNK5jmsYKYAu8ZD5QeVfZZx64mqp9HEg== X-Received: by 2002:a05:600c:1d09:b0:3c6:e63d:adb3 with SMTP id l9-20020a05600c1d0900b003c6e63dadb3mr18795774wms.35.1671028666084; Wed, 14 Dec 2022 06:37:46 -0800 (PST) Received: from [192.168.10.46] (146725694.box.freepro.com. [130.180.211.218]) by smtp.googlemail.com with ESMTPSA id l6-20020a05600c4f0600b003a3442f1229sm3321055wmq.29.2022.12.14.06.37.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Dec 2022 06:37:45 -0800 (PST) Message-ID: Date: Wed, 14 Dec 2022 15:37:43 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH 0/4] thermal: fix locking regressions in linux-next Content-Language: en-US To: "Rafael J. Wysocki" , Johan Hovold Cc: Amit Kucheria , Thara Gopinath , Andy Gross , Bjorn Andersson , Konrad Dybcio , Zhang Rui , Bartlomiej Zolnierkiewicz , Krzysztof Kozlowski , Alim Akhtar , Thierry Reding , Jonathan Hunter , Dmitry Baryshkov , linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-tegra@vger.kernel.org References: <20221214131617.2447-1-johan+linaro@kernel.org> From: Daniel Lezcano In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 14/12/2022 15:02, Rafael J. Wysocki wrote: > On Wed, Dec 14, 2022 at 2:18 PM Johan Hovold wrote: >> >> This series fixes some of the fallout after the thermal changes that >> just landed in linux-next. >> >> Lockdep reported a lock inversion in one of the Qualcomm drivers and a >> closer review revealed that the changes had also broken the sysfs >> interface for at least three drivers. >> >> Note that a simple revert of the offending patches was not an option as >> some of the infrastructure that the old implementation relied on has >> also been removed. > > I've dropped that material from my linux-next branch and Daniel, > please also remove it from your branch that is pulled by linux-next so > that it doesn't show up in there until 6.2-rc1 is out. > > It clearly is not ready for merging in its current form. I rebased a linux-next branch without the generic trip points rework. It can be inverted with the other changes without conflicts. I've pushed the branch in case you want to have a look. If you think it is acceptable in this form, I can send a tagged PR for 6.2-rc1 again. > It is still present in my bleeding-edge branch, though, so please > apply the patches from Johan on top of it and send a new PR to me, so > I can add it back to my linux-next branch once 6.2-rc1 appears. > > It would be good to check the code again too for any more similar fallout. I've been through already, the exynos fix is not necessary. But anyway, I agree we should keep these changes for the next release, it is better. -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog