Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 20 Sep 2022 09:28:50 -0700
From:   Guru Das Srinagesh <quic_gurus@quicinc.com>
To:     Bjorn Andersson <andersson@kernel.org>
CC:     Andy Gross <agross@kernel.org>,
        Konrad Dybcio <konrad.dybcio@somainline.org>,
        <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] soc: qcom: llcc: Move struct llcc_slice_config to
 header
Message-ID: <20220920162849.GA27067@quicinc.com>
References: <1663384000-8097-1-git-send-email-quic_gurus@quicinc.com>
 <20220919205633.qw5ucwjtyt4vjsro@builder.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20220919205633.qw5ucwjtyt4vjsro@builder.lan>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk

On Sep 19 2022 15:56, Bjorn Andersson wrote:
> On Fri, Sep 16, 2022 at 08:06:40PM -0700, Guru Das Srinagesh wrote:
> > Move struct llcc_slice_config to header so that it can be reused by
> > other kernel modules.
> 
> Can you please continue this sentence to provide some concrete examples?
> Will we see those other users posted upstream?

There is an llcc debug module downstream that we're currently using to test the
llcc driver that uses this struct and has to copy the struct definition because
it's not in the header. I can check with the team about their plans to upstream
this driver.

Thank you.

Guru Das.