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 DAAAEC4332F for ; Tue, 29 Nov 2022 05:54:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235610AbiK2FyB (ORCPT ); Tue, 29 Nov 2022 00:54:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235634AbiK2Fx7 (ORCPT ); Tue, 29 Nov 2022 00:53:59 -0500 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5CE814FFAF for ; Mon, 28 Nov 2022 21:53:57 -0800 (PST) Received: by mail-pj1-x1033.google.com with SMTP id hd14-20020a17090b458e00b0021909875bccso416168pjb.1 for ; Mon, 28 Nov 2022 21:53:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=user-agent: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=QGUEPx1xzxhjCBjmyfak65lMBIhLucPqClHTEgv0v+Q=; b=VwfG/CQdnAymgSvzcRNNCSRZrRkblh4qro+UykiPwg0yquXUtChJ1t0+eAeOC2m54g 9H5541QUKuRXUmcQjNkTZ86LBsxKqY+FI5vLZCgiJcsRyHJBbVrff0Szv7O37DtNbGGj mwXUUk+t7+jrh4nWqywyqo+LB5PoyM46jbQBybzkF4MapNsD8MOAe9Em3tnOpoFZgI9J 9IJcGj+BgB6X+FAVduyqT6sSuX8HjoWQqK8IrJWIJ2z2U6byMvWoN2i9Z8n7o0yP2ubh 5dcD3Ds0vboDBrp8VM9rJ1r0HJOplIzSrPIhRQ+WPXnoRWs1T9wthISuCoBICaugiIlO O1Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent: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=QGUEPx1xzxhjCBjmyfak65lMBIhLucPqClHTEgv0v+Q=; b=2VPn3KmmEbm1/u5+i4sQduUT9J12w8B5JQPt6qhb4mO+Nv52G/cbYM/K3k6GbGV0Wl jFOxFcsnfGEkB06mSahkxsnNNTJiK8tsA9P7T13cw/RfhDnUxeH+w4+0aVWGYx3JRpyB AbVllBpGO+vrJ8ETMxxZzA8NUz2MiZjtyBfqOzjpImbU0M3jpVrNBvGUMhX3t/7pMtxH EsW30+6k8xJFpIfPGwDCCz9ZAP1SP0zzJQ741PgIbZ9E9ek4Q3iTRrghQmJSid+cI+xq YWJbEhugEXOTXQ2fJhNLLJUaz4rg8QlNxrJj6xY/68dELh36g7eD69h2GfayQyxqMRB1 SFrw== X-Gm-Message-State: ANoB5pnCokTa8rXg9R2WysT4sCocF9rTz6uswfBuFxs73KdKK3eMsfSc Z5Z4jJbJffRXO85jM1dBUlCS X-Google-Smtp-Source: AA0mqf4agF2oc0K3ovVJmPb81+pPhrHenKyRWvpFKt8Me3twmKftFTAZIzSSqrl0TGA3bY5+Z5p9NQ== X-Received: by 2002:a17:90a:4745:b0:213:1442:24be with SMTP id y5-20020a17090a474500b00213144224bemr62656499pjg.15.1669701236727; Mon, 28 Nov 2022 21:53:56 -0800 (PST) Received: from workstation ([117.207.29.115]) by smtp.gmail.com with ESMTPSA id h7-20020a632107000000b0044046aec036sm7614112pgh.81.2022.11.28.21.53.52 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 28 Nov 2022 21:53:55 -0800 (PST) Date: Tue, 29 Nov 2022 11:23:51 +0530 From: Manivannan Sadhasivam To: Borislav Petkov Cc: bjorn.andersson@linaro.org, mchehab@kernel.org, james.morse@arm.com, rric@kernel.org, linux-arm-msm@vger.kernel.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org, quic_saipraka@quicinc.com Subject: Re: [PATCH v4 1/2] EDAC/qcom: Get rid of hardcoded register offsets Message-ID: <20221129055351.GA4931@workstation> References: <20221116143352.289303-1-manivannan.sadhasivam@linaro.org> <20221116143352.289303-2-manivannan.sadhasivam@linaro.org> <20221128181705.GP62721@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On Mon, Nov 28, 2022 at 07:35:14PM +0100, Borislav Petkov wrote: > On Mon, Nov 28, 2022 at 11:47:05PM +0530, Manivannan Sadhasivam wrote: > > Well, yes but that would imply both LLCC and EDAC patches going together. > > Splitting them will break the build, which is worse. > > Sounds like you need to check out: > > Documentation/process/stable-kernel-rules.rst > > first. > > Hint: there are provisions in there how to specify dependencies between > commits. > Hmm, I did miss reading this. Thanks for pointing out. > > Sorry, it is because I only tried building for ARM64 architecture. The > > error you are seeing is for x86-64 and I could now reproduce it as > > well. > > Yes, because arch doesn't matter here - the .config does. > Well, arch does matter here. LLCC driver depends on ARCH_QCOM || COMPILE_TEST. In the case of ARCH_QCOM, the REGMAP_MMIO is implicitly selected and you won't see the error with built-in or as a module. Only if you unselect ARCH_QCOM and use x86_64 (or any other arch) with COMPILE_TEST, then you'll see the error with both built-in and module. > Therefore, as requested: > > "For the next version, you'd need to fix all possible Kconfig build > errors before sending." > Sure. Thanks, Mani > Thx. > > -- > Regards/Gruss, > Boris. > > https://people.kernel.org/tglx/notes-about-netiquette