linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bijan Tabatabai <bijan311@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	 BIJAN TABATABAI <btabatabai@wisc.edu>,
	akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
	 brauner@kernel.org, mingo@redhat.com,
	Liam Howlett <liam.howlett@oracle.com>,
	 Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>
Subject: Re: [RFC PATCH 0/4] Add support for File Based Memory Management
Date: Sun, 24 Nov 2024 10:53:50 -0600	[thread overview]
Message-ID: <CAMvvPS4nPawexGND2YCc_a2CPA6fCb31xS-+1Ng54fVB6h9hig@mail.gmail.com> (raw)
In-Reply-To: <b33f00ed-9c63-48b3-943d-50f517644486@lucifer.local>

On Sat, Nov 23, 2024 at 6:23 AM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> + VMA guys, it's important to run scripts/get_maintainers.pl on your
> changes so the right people are pinged :)

Sorry about that. I'll be more mindful of this next time I send a patch.

> While it's a cool project, I don't think it's upstreamable in its current
> form - it essentially bypasses core mm functionality and 'does mm'
> somewhere else (which strikes me, in effect, as the entire purpose of the
> series).

Understandable.
Thank you for spending the time to review the patches and giving a
thorough reply!

Bijan


  reply	other threads:[~2024-11-24 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 20:38 Bijan Tabatabai
2024-11-22 20:38 ` [RFC PATCH 1/4] mm: " Bijan Tabatabai
2024-11-22 20:38 ` [RFC PATCH 2/4] fbmm: Add helper functions for FBMM MM Filesystems Bijan Tabatabai
2024-11-22 20:38 ` [RFC PATCH 3/4] mm: Export functions for writing " Bijan Tabatabai
2024-11-22 20:38 ` [RFC PATCH 4/4] Add base implementation of an MFS Bijan Tabatabai
2024-12-02 15:56   ` Jeff Johnson
2024-11-23 12:23 ` [RFC PATCH 0/4] Add support for File Based Memory Management Lorenzo Stoakes
2024-11-24 16:53   ` Bijan Tabatabai [this message]
2024-11-28 10:22   ` David Hildenbrand

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=CAMvvPS4nPawexGND2YCc_a2CPA6fCb31xS-+1Ng54fVB6h9hig@mail.gmail.com \
    --to=bijan311@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=btabatabai@wisc.edu \
    --cc=jannh@google.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mingo@redhat.com \
    --cc=vbabka@suse.cz \
    --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