From: Oleg Nesterov <oleg@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Yonghong Song <yonghong.song@linux.dev>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kui-Feng Lee <sinquersw@gmail.com>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v2 0/5] bpf: task_group_seq_get_next: misc cleanups
Date: Thu, 7 Sep 2023 08:44:41 +0200 [thread overview]
Message-ID: <20230907064440.GA352@redhat.com> (raw)
In-Reply-To: <CAADnVQJw81i+Qe0fveT07K39YkMA4xocQGZBmu=FbT+17sjxdg@mail.gmail.com>
On 09/06, Alexei Starovoitov wrote:
>
> On Tue, Sep 5, 2023 at 12:59 PM Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > > The next (final) patch will change this code to use __next_thread when
> > >
> > > https://lore.kernel.org/all/20230824143142.GA31222@redhat.com/
> > >
> > > is merged.
>
> The patch set looks fine.
> What is the next step?
> Should we merge it now in bpf-next and then during the next merge window
> you'll follow up with __next_thread clean up?
Thanks, works for me.
Oleg.
next prev parent reply other threads:[~2023-09-07 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 15:46 [PATCH bpf-next v2 0/5] bpf: task_group_seq_get_next: misc cleanups Oleg Nesterov
2023-09-05 15:46 ` [PATCH bpf-next v2 1/5] bpf: task_group_seq_get_next: cleanup the usage of next_thread() Oleg Nesterov
2023-09-05 15:46 ` [PATCH bpf-next v2 2/5] bpf: task_group_seq_get_next: cleanup the usage of get/put_task_struct Oleg Nesterov
2023-09-05 15:46 ` [PATCH bpf-next v2 3/5] bpf: task_group_seq_get_next: fix the skip_if_dup_files check Oleg Nesterov
2023-09-05 15:46 ` [PATCH bpf-next v2 4/5] bpf: task_group_seq_get_next: kill next_task Oleg Nesterov
2023-09-05 15:46 ` [PATCH bpf-next v2 5/5] bpf: task_group_seq_get_next: simplify the "next tid" logic Oleg Nesterov
2023-09-05 19:58 ` [PATCH bpf-next v2 0/5] bpf: task_group_seq_get_next: misc cleanups Oleg Nesterov
2023-09-06 20:00 ` Alexei Starovoitov
2023-09-07 6:44 ` Oleg Nesterov [this message]
2023-09-07 16:00 ` 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=20230907064440.GA352@redhat.com \
--to=oleg@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=sinquersw@gmail.com \
--cc=yonghong.song@linux.dev \
/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