From: Jakub Kicinski <kuba@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Matthieu Baerts <matthieu.baerts@tessares.net>,
dhowells@redhat.com, acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, bpf@vger.kernel.org,
davem@davemloft.net, irogers@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-perf-users@vger.kernel.org, mark.rutland@arm.com,
mingo@redhat.com, netdev@vger.kernel.org, peterz@infradead.org,
sfr@canb.auug.org.au
Subject: Re: [PATCH net-next] perf trace: fix MSG_SPLICE_PAGES build error
Date: Mon, 26 Jun 2023 14:49:34 -0700 [thread overview]
Message-ID: <20230626144934.4904c2ad@kernel.org> (raw)
In-Reply-To: <CAM9d7che_3z=NgT9OkrNmAQigY3Bo8nv16TVH6fgx8pn76xUbg@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-06-26 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 1:28 linux-next: build failure after merge of the net-next tree Stephen Rothwell
2023-06-26 7:48 ` David Howells
2023-06-26 8:12 ` Stephen Rothwell
2023-06-26 9:02 ` [PATCH net-next] perf trace: fix MSG_SPLICE_PAGES build error Matthieu Baerts
2023-06-26 21:27 ` Jakub Kicinski
2023-06-26 21:41 ` Namhyung Kim
2023-06-26 21:49 ` Jakub Kicinski [this message]
2023-06-27 3:31 ` Matthieu Baerts
2023-06-27 14:10 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230626144934.4904c2ad@kernel.org \
--to=kuba@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthieu.baerts@tessares.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.