linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hooanon05g@gmail.com
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [GIT PULL] acl updates for v6.2
Date: Wed, 04 Jan 2023 09:57:28 +0900	[thread overview]
Message-ID: <16855.1672793848@jrobl> (raw)
In-Reply-To: <20221227183115.ho5irvmwednenxxq@wittgenstein>

Christian Brauner:
> On Wed, Dec 28, 2022 at 12:27:55AM +0900, J. R. Okajima wrote:
	:::
> > I've found a behaviour got changed from v6.1 to v6.2-rc1 on ext3 (ext4).
>
> Hey, I'll try to take a look before new years.

Now it becomes clear that the problem was on my side.
The "acl updates for v6.2" in mainline has nothing to deal with it.
Sorry for the noise.


J. R. Okajima

  parent reply	other threads:[~2023-01-04  0:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 11:19 [GIT PULL] acl updates for v6.2 Christian Brauner
2022-12-13  2:56 ` Linus Torvalds
2022-12-13  9:09   ` Christian Brauner
2022-12-13  3:49 ` pr-tracker-bot
2022-12-27 15:27 ` J. R. Okajima
2022-12-27 18:31   ` Christian Brauner
2022-12-27 23:54     ` hooanon05g
2023-01-04  0:57     ` hooanon05g [this message]
2023-01-04 10:04       ` Linux kernel regression tracking (#info)
2023-01-04 10:14         ` Christian Brauner
2023-01-04 10:26           ` Thorsten Leemhuis
2023-01-04 10:37             ` Christian Brauner
2022-12-28  8:40   ` [GIT PULL] acl updates for v6.2 #forregzbot Thorsten Leemhuis
2023-01-01 20:07     ` J. R. Okajima
2023-01-02  7:25       ` Thorsten Leemhuis

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=16855.1672793848@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.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;
as well as URLs for NNTP newsgroup(s).