All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Paul Moore <paul@paul-moore.com>,
	 linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	 Stephen Smalley <stephen.smalley.work@gmail.com>,
	 linux-kernel@vger.kernel.org, selinux@vger.kernel.org,
	 eggert@cs.ucla.edu,  bug-gnulib@gnu.org
Subject: Re: [PATCH] fs/xattr.c: fix simple_xattr_list()
Date: Mon, 16 Jun 2025 17:27:57 -0700	[thread overview]
Message-ID: <875xgv6wky.fsf@gmail.com> (raw)
In-Reply-To: <20250616-flitzen-barmherzigen-e30c63f9e8ba@brauner>

Christian Brauner <brauner@kernel.org> writes:

>> Checking on the status of this patch as we are at -rc2 and I don't see
>> it in Linus' tree?
>
> Sent this morning with some other fixes.

I see it merged now [1].

Thanks for the help all.

Collin

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe78e02600f83d81e55f6fc352d82c4f264a2901

  reply	other threads:[~2025-06-17  0:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:48 [PATCH] fs/xattr.c: fix simple_xattr_list() Stephen Smalley
2025-06-05 21:40 ` Paul Moore
2025-06-05 21:51   ` Paul Moore
2025-06-06  5:39     ` Collin Funk
2025-06-10 23:50       ` Paul Moore
2025-06-11 10:05         ` Christian Brauner
2025-06-11 15:45           ` Paul Moore
2025-06-12 12:21             ` Christian Brauner
2025-06-12 12:54               ` Stephen Smalley
2025-06-16 14:03           ` Paul Moore
2025-06-16 14:13             ` Christian Brauner
2025-06-17  0:27               ` Collin Funk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-05 16:51 Stephen Smalley
2025-06-05 17:09 ` Collin Funk

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=875xgv6wky.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=brauner@kernel.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.