[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVdF8S_dsktOaRM49st+tfyrx6NPK8k2AK96-v=G6LYzw@mail.gmail.com>
Date: Fri, 22 Nov 2024 10:47:54 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "Theodore Ts'o" <tytso@....edu>
Cc: Kent Overstreet <kent.overstreet@...ux.dev>, Shuah Khan <skhan@...uxfoundation.org>,
Michal Hocko <mhocko@...e.com>, Dave Chinner <david@...morbit.com>,
Andrew Morton <akpm@...ux-foundation.org>, Christoph Hellwig <hch@....de>,
Yafang Shao <laoar.shao@...il.com>, jack@...e.cz, Christian Brauner <brauner@...nel.org>,
Alexander Viro <viro@...iv.linux.org.uk>, Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>, "Serge E. Hallyn" <serge@...lyn.com>, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-bcachefs@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org,
"conduct@...nel.org" <conduct@...nel.org>
Subject: Re: [PATCH 1/2 v2] bcachefs: do not use PF_MEMALLOC_NORECLAIM
On Thu, Nov 21, 2024 at 12:49 AM Theodore Ts'o <tytso@....edu> wrote:
> If you look at the git history of the kernel sources, you will see
> that a large number of your fellow maintainers assented to this
> approach --- for example by providing their Acked-by in commit
> 1279dbeed36f ("Code of Conduct Interpretation: Add document explaining
> how the Code of Conduct is to be interpreted").
404
The correct reference is commit 79dbeed36f7335ec ("Code of Conduct
Interpretation: Add document explaining how the Code of Conduct is to
be interpreted").
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists