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 BE776C636CD for ; Tue, 7 Feb 2023 04:15:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230322AbjBGEPX (ORCPT ); Mon, 6 Feb 2023 23:15:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37548 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229807AbjBGEPR (ORCPT ); Mon, 6 Feb 2023 23:15:17 -0500 Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C8363526C for ; Mon, 6 Feb 2023 20:15:16 -0800 (PST) Received: by mail-pl1-x62a.google.com with SMTP id m2so14428519plg.4 for ; Mon, 06 Feb 2023 20:15:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=OuzFX3QClT0cgHFkVJpN63xKVFqWgVKjkLO80TI1u6E=; b=T1I34N7FeZezC00Co2Ev65+CBbGAL//mqs5yrTfsIgGkm94BSqAyCLiF6kxYZbHmSv 8wnrtuVoMAR89Du8ShqKPjtvzQL03mTqbvW/rP75KsUxfzhTuaQu7jSAyJyThMxn9UwZ /PGyGFV9Yuf8lHNXDwKMIP++3OVQj4dWkUEjGZ28WPC2ygXsFGoCEnHtNw6CwAdogIJj jFMTd/mY/FiqWBbjicnORQk5vzr0/zzVtK/eUVZJ8OGr+KZQy9fuDjPxQxIGxSs7UWkO RLV2Bn3tGVuYbq3LjL3Bs/5fC0zUkcrAL6E41aDBgpOhfvuaULBCJOgoFJj/EIG7Fvvb SPYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=OuzFX3QClT0cgHFkVJpN63xKVFqWgVKjkLO80TI1u6E=; b=zaCM6cDGBMIis2ztosdQDeiAdFSB5ACvNqzbVev0hXBm3Sv4tY2K5YE04hOsOq8N/N GNj4pCiqulzLOcZ/7C9pHKRcXRKB5Us/V5LgAjAdz+Lrqw72GWy6aC0XQIkuwFwgHpLg RUGCe2Gd5r2eZtDElrJxCC+ge9Vp6KHm/giYkGdCGLSiZHA57Xz7EP+0n9/ktPo1uNAD PfBBWRg1Q4hSVsq9OEUquvB1q1FldWJgORi00jogIfr8M5bsF63Fj2wmh0Bw3CLWNJ1l c/iLRL2cnvMYZ7IDUhCimLSsjFpbFDoB075/8L5qBPUrosQv/oXYbv+yoKAtUg2DZm/5 FRIw== X-Gm-Message-State: AO0yUKWCE6A41pJwec7hUek79PNAvMvzBsDAVAAOgKIYSD7gKvHF1OI1 xciUe9sr5q4Yz1PD9LPA6SyFgg== X-Google-Smtp-Source: AK7set9ciXhDCMZkykgPEO4CCITs6Emh/6AddwMq1SkdRa5BbV92+7D5Og7Wi/h5YGkVorM5U+y0Fw== X-Received: by 2002:a17:903:189:b0:196:3bbb:e9e3 with SMTP id z9-20020a170903018900b001963bbbe9e3mr1664498plg.28.1675743315652; Mon, 06 Feb 2023 20:15:15 -0800 (PST) Received: from localhost ([122.172.83.155]) by smtp.gmail.com with ESMTPSA id jc5-20020a17090325c500b00194afb5a3ebsm3956615plb.21.2023.02.06.20.15.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Feb 2023 20:15:14 -0800 (PST) Date: Tue, 7 Feb 2023 09:45:12 +0530 From: Viresh Kumar To: Bjorn Andersson Cc: Robert Marko , ilia.lin@kernel.org, agross@kernel.org, konrad.dybcio@linaro.org, rafael@kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org Subject: Re: [PATCH 2/4] cpufreq: qcom-nvmem: reuse socinfo SMEM item struct Message-ID: <20230207041512.rxeeg52wduxsfgk7@vireshk-i7> References: <20230121112947.53433-1-robimarko@gmail.com> <20230121112947.53433-2-robimarko@gmail.com> <20230206203816.afexndkiqhpk6e7b@ripper> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230206203816.afexndkiqhpk6e7b@ripper> Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 06-02-23, 12:38, Bjorn Andersson wrote: > On Sat, Jan 21, 2023 at 12:29:45PM +0100, Robert Marko wrote: > > Now that socinfo SMEM item struct and defines have been moved to a header > > so we can utilize that instead. > > > > Now the SMEM value can be accesed directly, there is no need for defining > > the ID for the SMEM request as well. > > > > Signed-off-by: Robert Marko > > Reviewed-by: Bjorn Andersson > > @Rafael, @Viresh, would you mind providing an Ack for me to take these 3 > patches, together with patch 1, through the Qualcomm tree? I have staged > changes for 6.3, so we'll otherwise end up with conflicts on the move of > the struct. For all cpufreq patches. Acked-by: Viresh Kumar -- viresh