From: Christian Brauner via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Mark Fasheh <mark@fasheh.com>
Cc: Arnd Bergmann <arnd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ocfs2-devel <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: reduce ioctl stack usage
Date: Mon, 24 Apr 2023 10:24:55 +0200 [thread overview]
Message-ID: <20230424-handtaschen-armut-91885793ecf1@brauner> (raw)
In-Reply-To: <CAGe7X7mLU0JOftGVA+NHabu-9a=fuaofy+KhpvCJFnkRz5ANtQ@mail.gmail.com>
On Thu, Apr 20, 2023 at 10:01:12AM -0700, Mark Fasheh wrote:
> On Thu, Apr 20, 2023 at 2:34 AM Christian Brauner <brauner@kernel.org> wrote:
> > I think I might not have communicated as clearly as I should have.
> > Simply because I naively assumed that this is unproblematic.
> >
> > By "we" I mean people responsible for "fs/" which now happens to also
> > include me. So the goal of this is for patches falling under fs/ to get
> > picked up more quickly and broadly and share the maintenance burden.
>
> Did you get buy-in from other folks in 'fs/'? What other projects are
> you carrying? Granted I'm a bit out of the loop these days but this is
> the first I'm hearing of this.
>
> Andrew has a well oiled machine going, so if he's still ok carrying
> the patches then that's where I'd like them until such time that you
> can provide a tangible benefit.
A patch is sent for something that falls under the fs/ directory. In
this case fs/ocfs2/. The maintainer's of fs/ocfs2/ provide their acks.
A maintainer - In this case my sorry ass - of fs/ looks into the
maintainer's file to make sure that someone will pick up those patches
by looking for a tree entry under the respective fs/ocfs2/ entry.
There is no tree entry.
So the patch is picked up by a respective maintainer of fs/ to ensure
that fixes land in mainline.
So, if you have a tree that you think fs/ocfs2/ belongs to then please
send a patch to add the respective tree into the maintainer's file.
This is especially true when fs/ stuff surprisingly goes via mm/. I
don't want to have to guess what tree you're going through even if it's
been going on for a long time.
There are no bad intentions here but please clarify the ocfs2 entry in
the maintainer's file.
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2023-04-24 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:56 [Ocfs2-devel] [PATCH] ocfs2: reduce ioctl stack usage Arnd Bergmann via Ocfs2-devel
2023-04-18 1:44 ` Joseph Qi via Ocfs2-devel
2023-04-18 2:29 ` Mark Fasheh via Ocfs2-devel
[not found] ` <20230418-fortgehen-inkubationszeit-5d3db3f0c2b1@brauner>
2023-04-18 9:37 ` Joseph Qi via Ocfs2-devel
2023-04-18 12:56 ` Christian Brauner via Ocfs2-devel
2023-04-18 18:02 ` Theodore Ts'o via Ocfs2-devel
2023-04-19 2:00 ` Joseph Qi via Ocfs2-devel
2023-04-19 21:21 ` Andrew Morton via Ocfs2-devel
2023-04-20 9:34 ` Christian Brauner via Ocfs2-devel
2023-04-20 17:01 ` Mark Fasheh via Ocfs2-devel
2023-04-24 8:24 ` Christian Brauner via Ocfs2-devel [this message]
2023-04-20 20:48 ` Al Viro via Ocfs2-devel
2023-04-24 8:10 ` Christian Brauner via Ocfs2-devel
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-handtaschen-armut-91885793ecf1@brauner \
--to=ocfs2-devel@oss.oracle.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).