From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Christian Brauner <brauner@kernel.org>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Arnd Bergmann <arnd@kernel.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: Wed, 19 Apr 2023 14:21:59 -0700 [thread overview]
Message-ID: <20230419142159.fd5ca2e91658fe304e317a72@linux-foundation.org> (raw)
In-Reply-To: <d1e719ea-95bf-bb96-62db-e550cefe0a80@linux.alibaba.com>
On Wed, 19 Apr 2023 10:00:15 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
>
>
> On 4/18/23 8:56 PM, 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.
>
> Either is fine for me.
> Hi Andrew, what's your opinion?
I've been wrangling ocfs2 for over a decade and this is the first I've
heard of this proposal.
Who is "we", above? What was their reasoning?
Who will be responsible for ocfs2 patches? What will be their workflow
and review and test processes?
Overall, what benefit does this proposal offer the ocfs2 project?
next prev parent reply other threads:[~2023-04-19 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:56 [PATCH] ocfs2: reduce ioctl stack usage 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 [this message]
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
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=20230419142159.fd5ca2e91658fe304e317a72@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=brauner@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 \
/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