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, 6 Jun 2023 14:24:36 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Arnaldo Carvalho de Melo <acme@kernel.org>
Cc:     Ravi Bangoria <ravi.bangoria@amd.com>,
        Peter Zijlstra <peterz@infradead.org>, irogers@google.com,
        suzuki.poulose@arm.com, mike.leach@linaro.org, leo.yan@linaro.org,
        john.g.garry@oracle.com, will@kernel.org, james.clark@arm.com,
        mingo@redhat.com, mark.rutland@arm.com,
        alexander.shishkin@linux.intel.com, jolsa@kernel.org,
        namhyung@kernel.org, adrian.hunter@intel.com, kjain@linux.ibm.com,
        renyu.zj@linux.alibaba.com, kan.liang@linux.intel.com,
        zhengjun.xing@linux.intel.com, maddy@linux.ibm.com,
        atrajeev@linux.vnet.ibm.com, wangming01@loongson.cn,
        chenhuacai@kernel.org, sandipan.das@amd.com, 9erthalion6@gmail.com,
        seanjc@google.com, robh@kernel.org, tmricht@linux.ibm.com,
        tegongkang@gmail.com, linux-kernel@vger.kernel.org,
        coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
        linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] perf test amd: Fix build failure with
 amd-ibs-via-core-pmu.c
Message-ID: <20230606142436.153750d9@canb.auug.org.au>
In-Reply-To: <ZH3w7TWRQZsPqhB2@kernel.org>
References: <CAP-5=fUPZ7+nAcxBp5sFBfxzkOH8kzWkLV0uziHqxYC0cDbbDw@mail.gmail.com>
        <20230603044650.286-1-ravi.bangoria@amd.com>
        <ZH3w7TWRQZsPqhB2@kernel.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/aoAnzQewuA0W1vppZT1azH0";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/aoAnzQewuA0W1vppZT1azH0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Arnaldo,

On Mon, 5 Jun 2023 11:27:57 -0300 Arnaldo Carvalho de Melo <acme@kernel.org=
> wrote:
>
> How are things like this resolved in linux-next?

Well, if it produces a conflict (or a build failure due to a semantic
conflict) I will fix it up (maybe using a separate patch such as this)
and report it so that the maintainers know that they need to let Linus
know about this when he merges their trees.

But since neither of those things has happened (it seems that an
allmodconfig build does not build the tests), I can still take this
patch and use it to fix up the tip tree merge (since that happens after
the perf tree merge) starting tomorrow and report it as above.  I will
then keep applying this patch to the merge until it is no longer needed.

Please send me the actual patch. (I am assuming that the patch applies
on top of a recent linux-next release?)

--=20
Cheers,
Stephen Rothwell

--Sig_/aoAnzQewuA0W1vppZT1azH0
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmR+tQQACgkQAVBC80lX
0GzQ8Qf/ZW/gJJZFgOOwSWU2eipr6GmHsFTkIhuD35t3ZI89Tb4IF30BT0nPctn/
WnZ05rwhdC6JkmTUfwWfOEfhUoQvXoGezQjtgwpZPRbUgyiU0NlSW1SKUFcXIaTJ
Q/1hBC2/sPGHII3JKcjBQMKw8haenmzuaAvdwTIyvVfDPUqQlxQzOUwgnxIDbcK8
eQL4nFwAIkhO2ZmKBjy1dh8bO9z9b80bJbFTwGeTMwlRotTkfNE0WYXsEFzKQkgF
OzrUacO20azqJcNn1pucBcHEueZhXbMQwB1lB74cwIrUKvoNeUy59fC63cwKEgVT
t8HnVqyrE2+WFoGNGfPyu9IWP/dh/A==
=E5lh
-----END PGP SIGNATURE-----

--Sig_/aoAnzQewuA0W1vppZT1azH0--