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 X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 041E0C3A59B for ; Mon, 19 Aug 2019 06:47:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C942E2086C for ; Mon, 19 Aug 2019 06:47:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="djIUAz1n" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726366AbfHSGrj (ORCPT ); Mon, 19 Aug 2019 02:47:39 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:43439 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725536AbfHSGrj (ORCPT ); Mon, 19 Aug 2019 02:47:39 -0400 Received: by mail-pg1-f195.google.com with SMTP id k3so610276pgb.10 for ; Sun, 18 Aug 2019 23:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=U24j4drPE5otk7nf5gewos8QdH/rOYJfvY6KgflN9k0=; b=djIUAz1ndxEIlY+kxK+HTygHu8sR9iy1wPvGqaJ1mtbb8X0DgRD9X2//23gMkBQUnD byvxccJJhxvV91/H0YrNZczq2d5loRKnk/dwv5tf21upV3w/560zShjzVcL+LPqGKvfg nPXTWn+R2stP9ZDzciiNwl+E5/5IBP+u95pLoMFrwqn0saB/vU4dzJQLDx3VeN1ec+IR CkmlmwsQAXNmoUlIfvojXprQjvt8S7lntpMpLVqXC3orRClFXTRgY6e259WWjqMd0KZq t7k16eclKQlQBpERAi5eS3xnOCiNLsT+RYYWVlqbEtPTKm/D33mPdgodYvg+ViLwCVGi 1+JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=U24j4drPE5otk7nf5gewos8QdH/rOYJfvY6KgflN9k0=; b=VzJQAVl7eSuigWY268T84kOKOTEYrNK3sgc+RVW/tacd3nUe23nOXmhrmfHznG87Tf AYZB20IfgLlfIB2mtdz3XEJfFp2XiXo1/N1XxO7ALfE6E1K7y7/69la9iLL14xhEDfjE 9jTNKdyy0l5q07S4l2P9+xPkQFvT4i5ODli7KzMzdelya+NEhTvbtENL7zUxAx/TnFzZ ZGu1dtrQEvVOXGgg9iq4M6R80Y1uMgYXfJGqrJ35FiqrsaT6+7d/8swYsaBa02F5663L 91ZP5sHiqUXIvQ+IJ0uhtMwviFxflOQVUhEg2NpfH7JJf2VThn0gCJkjQ2fU1qFI6SuU Kezw== X-Gm-Message-State: APjAAAVP5RP5+nr9VLp58Qh6OnGNsQYCCOa3/8ghNQpX4FzZJheHmEt7 sWRgAJOH8KHWGZ4XMAVJ7o3Pbg== X-Google-Smtp-Source: APXvYqyRm31hfZbfmLKyBsV9eWUiiBhiB0DVtxpye32kyhXYNAL+EDIedFCg3gtIe6UU3rEhkWhZjQ== X-Received: by 2002:a63:c008:: with SMTP id h8mr19094494pgg.427.1566197258253; Sun, 18 Aug 2019 23:47:38 -0700 (PDT) Received: from localhost ([122.172.76.219]) by smtp.gmail.com with ESMTPSA id s24sm14118882pgm.3.2019.08.18.23.47.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Aug 2019 23:47:37 -0700 (PDT) Date: Mon, 19 Aug 2019 12:17:35 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Rafael Wysocki , Linux PM , Vincent Guittot , Linux Kernel Mailing List Subject: Re: [PATCH V2 04/10] cpufreq: powerpc_cbe: Switch to QoS requests instead of cpufreq notifier Message-ID: <20190819064735.da3np75ybf64wpbt@vireshk-i7> References: <524de8ace0596e68a24b57b3b4043c707db32ca7.1563862014.git.viresh.kumar@linaro.org> <20190809023445.xn3mlv5qxjgz6bpp@vireshk-i7> <20190819022614.oy5qdozde2afibwu@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On 19-08-19, 08:42, Rafael J. Wysocki wrote: > OK, thanks! > > The series is on hold, though, because the acpi-cpufreq patch turned > out to be problematic and I didn't have the time to have a deeper look > at the problem last week. And so was I wondering why it is present in bleeding-edge only :) I don't think I am cc'd to any bug reports on that, can you please help me with some information on it ? -- viresh