From: Quentin Monnet <quentin@isovalent.com>
To: Mark Brown <broonie@kernel.org>, Heiko Carstens <hca@linux.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Howlett <liam.howlett@oracle.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Thomas Richter <tmricht@linux.ibm.com>,
bpf@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] bpftool: fix broken compile on s390 for linux-next repository
Date: Fri, 14 Apr 2023 17:58:21 +0100 [thread overview]
Message-ID: <82a4f1fe-14a7-4493-2fa7-8dac0bebf1dc@isovalent.com> (raw)
In-Reply-To: <9d3489e4-764c-4a42-9064-869fc5d6e0dc@sirena.org.uk>
Hi Mark,
2023-04-14 17:53 UTC+0100 ~ Mark Brown <broonie@kernel.org>
> On Fri, Apr 14, 2023 at 10:47:02AM +0200, Heiko Carstens wrote:
>> Full quote below for reference.
>>
>> Mark or Stephen could you please add the patch below to linux-next?
>
> Could someone please send me whatever patch is being referenced here?
> This looks like a quoted backtrace of some discussion.
Here it is on Patchwork:
https://patchwork.kernel.org/project/netdevbpf/patch/20230412123636.2358949-1-tmricht@linux.ibm.com/
Lore:
https://lore.kernel.org/all/20230412123636.2358949-1-tmricht@linux.ibm.com/
Thanks,
Quentin
next prev parent reply other threads:[~2023-04-14 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 12:36 [PATCH] bpftool: fix broken compile on s390 for linux-next repository Thomas Richter
2023-04-12 13:27 ` Quentin Monnet
2023-04-14 8:47 ` Heiko Carstens
2023-04-14 16:53 ` Mark Brown
2023-04-14 16:58 ` Quentin Monnet [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 8:55 Thomas Richter
2023-04-18 9:13 ` Quentin Monnet
2023-04-19 14:50 ` Daniel Borkmann
2023-04-20 0:39 ` Quentin Monnet
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=82a4f1fe-14a7-4493-2fa7-8dac0bebf1dc@isovalent.com \
--to=quentin@isovalent.com \
--cc=acme@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=hca@linux.ibm.com \
--cc=liam.howlett@oracle.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tmricht@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox