[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230626144934.4904c2ad@kernel.org>
Date: Mon, 26 Jun 2023 14:49:34 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>, Matthieu Baerts
<matthieu.baerts@...sares.net>, dhowells@...hat.com, acme@...nel.org,
adrian.hunter@...el.com, alexander.shishkin@...ux.intel.com,
bpf@...r.kernel.org, davem@...emloft.net, irogers@...gle.com,
jolsa@...nel.org, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux-perf-users@...r.kernel.org, mark.rutland@....com, mingo@...hat.com,
netdev@...r.kernel.org, peterz@...radead.org, sfr@...b.auug.org.au
Subject: Re: [PATCH net-next] perf trace: fix MSG_SPLICE_PAGES build error
On Mon, 26 Jun 2023 14:41:56 -0700 Namhyung Kim wrote:
> > Hi Arnaldo, are you okay with us taking this into the networking tree?
> > Or do you prefer to sync the header after everything lands in Linus's
> > tree?
>
> Arnaldo is on vacation now, and I'm taking care of the patches
> on behalf of him.
>
> As it's introduced in the networking tree, it should be fine to
> carry the fix together. I'll sync the header later.
Will do, thanks!
> But in general you don't need to change the copy of the tools
> headers together. It also needs to support old & new kernels
> so different care should be taken. Please separate tooling
> changes and let us handle them.
Ack, I'm not sure what makes this a special case, from Stephen's
original report:
https://lore.kernel.org/all/20230626112847.2ef3d422@canb.auug.org.au/
it sounded like perf won't build without the fix.
Powered by blists - more mailing lists