From: Luis Chamberlain <mcgrof@kernel.org>
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, daniel@iogearbox.net, kernel-team@fb.com,
x86@kernel.org, dave.hansen@linux.intel.com,
rick.p.edgecombe@intel.com
Subject: Re: [PATCH v6 bpf-next 0/5] bpf_prog_pack followup
Date: Thu, 7 Jul 2022 15:59:42 -0700 [thread overview]
Message-ID: <YsdlXjpRrlE9Z+Jq@bombadil.infradead.org> (raw)
In-Reply-To: <20220707223546.4124919-1-song@kernel.org>
On Thu, Jul 07, 2022 at 03:35:41PM -0700, Song Liu wrote:
> This set is the second half of v4 [1].
>
> Changes v5 => v6:
> 1. Rebase and extend CC list.
Why post a new iteration so soon without completing the discussion we
had? It seems like we were at least going somewhere. If it's just
to include mm as I requested, sure, that's fine, but this does not
provide context as to what we last were talking about.
Luis
next prev parent reply other threads:[~2022-07-07 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 22:35 [PATCH v6 bpf-next 0/5] bpf_prog_pack followup Song Liu
2022-07-07 22:35 ` [PATCH v6 bpf-next 1/5] module: introduce module_alloc_huge Song Liu
2022-07-07 22:35 ` [PATCH v6 bpf-next 2/5] bpf: use module_alloc_huge for bpf_prog_pack Song Liu
2022-07-07 22:35 ` [PATCH v6 bpf-next 3/5] vmalloc: WARN for set_vm_flush_reset_perms() on huge pages Song Liu
2022-07-07 22:35 ` [PATCH v6 bpf-next 4/5] vmalloc: introduce huge_vmalloc_supported Song Liu
2022-07-07 22:35 ` [PATCH v6 bpf-next 5/5] bpf: simplify select_bpf_prog_pack_size Song Liu
2022-07-07 22:59 ` Luis Chamberlain [this message]
2022-07-07 23:52 ` [PATCH v6 bpf-next 0/5] bpf_prog_pack followup Song Liu
2022-07-08 0:53 ` Luis Chamberlain
2022-07-08 1:36 ` Song Liu
2022-07-08 15:58 ` Luis Chamberlain
2022-07-08 19:58 ` Song Liu
2022-07-08 22:24 ` Luis Chamberlain
2022-07-09 1:14 ` Song Liu
2022-07-12 4:18 ` Luis Chamberlain
2022-07-12 4:24 ` Luis Chamberlain
2022-07-12 5:49 ` Song Liu
2022-07-12 19:04 ` Luis Chamberlain
2022-07-12 23:12 ` Song Liu
2022-07-12 23:42 ` Luis Chamberlain
2022-07-13 1:00 ` Song Liu
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=YsdlXjpRrlE9Z+Jq@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rick.p.edgecombe@intel.com \
--cc=song@kernel.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).