From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Joseph Qi <joseph.qi@linux.alibaba.com>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Arnd Bergmann <arnd@kernel.org>, akpm <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
ocfs2-devel <ocfs2-devel@oss.oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ocfs2: reduce ioctl stack usage
Date: Mon, 24 Apr 2023 10:10:25 +0200 [thread overview]
Message-ID: <20230424-unser-erden-693a29d7a388@brauner> (raw)
In-Reply-To: <20230420204801.GO3390869@ZenIV>
On Thu, Apr 20, 2023 at 09:48:01PM +0100, Al Viro wrote:
> On Tue, Apr 18, 2023 at 02:56:38PM +0200, Christian Brauner wrote:
> > On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote:
> > > Andrew picked ocfs2 patches into -mm tree before.
> >
> > Yup and that's fine obviously, but this belongs to fs/ and we're aiming
> > to take fs/ stuff through the dedicated fs trees going forward.
>
> Er... Assuming that there *is* an active fs tree for filesystem
> in question. Do you really want dedicated e.g. affs, adfs, etc.
> git trees - one for each filesystem in there?
No, that's not meant or want. What I meant is that when a filesystem
doesn't have a dedicated tree (and/or active maintainers) mentioned in
the maintainer's file then we pick up those patches just like we already
do today and have done.
prev parent reply other threads:[~2023-04-24 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:56 Arnd Bergmann
2023-04-18 1:44 ` Joseph Qi
2023-04-18 2:29 ` Mark Fasheh
[not found] ` <20230418-fortgehen-inkubationszeit-5d3db3f0c2b1@brauner>
2023-04-18 9:37 ` Joseph Qi
2023-04-18 12:56 ` Christian Brauner
2023-04-18 18:02 ` Theodore Ts'o
2023-04-19 2:00 ` Joseph Qi
2023-04-19 21:21 ` Andrew Morton
2023-04-20 9:34 ` Christian Brauner
2023-04-20 17:01 ` Mark Fasheh
2023-04-24 8:24 ` Christian Brauner
2023-04-20 20:48 ` Al Viro
2023-04-24 8:10 ` Christian Brauner [this message]
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=20230424-unser-erden-693a29d7a388@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®