From: Uladzislau Rezki <urezki@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
zkabelac@redhat.com, Matthew Sakai <msakai@redhat.com>,
linux-mm@kvack.org, dm-devel@lists.linux.dev
Subject: Re: [PATCH] mm: allow __GFP_RETRY_MAYFAIL in vmalloc
Date: Mon, 2 Mar 2026 10:50:38 +0100 [thread overview]
Message-ID: <aaVdbio9nwRW4L6t@pc636> (raw)
In-Reply-To: <aZ7hJi2-iATBD6GL@tiehlicka>
>
> Feel free to use this patch. But please note that I do not have any user
> so I couldn't test it. So make sure this is tested before posted for
> official inclusion.
>
Thank you. I will properly test it and apply my fixes if needed.
--
Uladzislau Rezki
prev parent reply other threads:[~2026-03-02 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:33 [PATCH] mm: allow __GFP_RETRY_MAYFAIL in vmalloc Mikulas Patocka
2026-02-21 1:19 ` SeongJae Park
2026-02-23 5:48 ` Anshuman Khandual
2026-02-23 19:02 ` Vishal Moola (Oracle)
2026-02-23 19:25 ` Mikulas Patocka
2026-02-23 20:07 ` Uladzislau Rezki
2026-02-23 22:08 ` Michal Hocko
2026-02-24 11:39 ` Uladzislau Rezki
2026-02-24 12:22 ` Michal Hocko
2026-02-24 14:03 ` Christoph Hellwig
2026-02-24 14:22 ` Shakeel Butt
2026-02-24 14:26 ` Christoph Hellwig
2026-02-24 14:34 ` Michal Hocko
2026-03-02 17:33 ` Mikulas Patocka
2026-02-24 15:38 ` Uladzislau Rezki
2026-02-24 15:44 ` Michal Hocko
2026-02-24 15:51 ` Michal Hocko
2026-02-24 16:07 ` Uladzislau Rezki
2026-02-25 8:33 ` Uladzislau Rezki
2026-02-25 11:46 ` Michal Hocko
2026-03-02 9:50 ` Uladzislau Rezki [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=aaVdbio9nwRW4L6t@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mpatocka@redhat.com \
--cc=msakai@redhat.com \
--cc=sj@kernel.org \
--cc=vishal.moola@gmail.com \
--cc=zkabelac@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.