containers.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Alexey Gladkov <legion@kernel.org>,
	 Linux Containers <containers@lists.linux.dev>
Subject: Re: [GIT PULL] ipc: per namespace ipc sysctl changes for v5.19
Date: Sun, 05 Jun 2022 17:11:07 -0500	[thread overview]
Message-ID: <87tu8y69s4.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <CAHk-=wh0ZYiQuCJmohyYpk99mch=Nb+_m4DWxBX03DQWnsvCZA@mail.gmail.com> (Linus Torvalds's message of "Fri, 3 Jun 2022 15:59:33 -0700")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Fri, Jun 3, 2022 at 10:21 AM Eric W. Biederman <ebiederm@xmission.com> wrote:
>>
>> These changes were sent for v5.18[1] but were dropped because some
>> additional cleanups were requested.  Linus has given his nod[2] to the
>> cleanups so I hope enough cleanups are present this time.
>
> Well, I'll be happier still when the next set of cleanups hits:
>
>    https://lore.kernel.org/all/CAHk-=wjJ2CP0ugbOnwAd-=Cw0i-q_xC1PbJ-_1jrvR-aisiAAA@mail.gmail.com/
>
> but yeah, that further cleanup series clearly wasn't quite ready yet.

Yes.  It came in during the merge window.  I have been keeping a weather
eye on it but I really haven't had a chance to look yet.

Eric

  reply	other threads:[~2022-06-05 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 17:21 [GIT PULL] ipc: per namespace ipc sysctl changes for v5.19 Eric W. Biederman
2022-06-03 22:59 ` Linus Torvalds
2022-06-05 22:11   ` Eric W. Biederman [this message]
2022-06-03 23:25 ` pr-tracker-bot

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=87tu8y69s4.fsf@email.froward.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=containers@lists.linux.dev \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).