From: Cyril Hrubis <chrubis@suse.cz>
To: Geetika M <geetika@linux.ibm.com>
Cc: Sachin P Bappalige <sachinpb@linux.vnet.ibm.com>,
pavrampu@linux.ibm.com, sachinp@linux.ibm.com,
ltp@lists.linux.it, pavithra.visweswara@ibm.com
Subject: Re: [LTP] Acceptance Status of libhugetlbfs Patches
Date: Mon, 2 Sep 2024 11:30:23 +0200 [thread overview]
Message-ID: <ZtWFr6OWSah0k4j0@yuki.lan> (raw)
In-Reply-To: <bf5ed5dc-805c-4825-898f-1e4d3d280f2c@linux.ibm.com>
Hi!
> I am writing on behalf of my team regarding the patches we recently
> submitted to the LTP mailing list. We wanted to follow up and inquire
> about the status of these patches and their potential integration into
> the upstream project.
>
> For your reference, here are the few links to the patches we have sent:
>
> *[LTP] [PATCH v2] [PATCH] Hugetlb: Migrating libhugetlbfs shm-perms
> <https://lore.kernel.org/ltp/20240510141020.189065-1-spoorthy@linux.ibm.com/>*
>
> *[LTP] [PATCH v4] Migrating the libhugetlbfs/testcases/shm-gettest.c
> test
> <https://lore.kernel.org/ltp/20240515092456.3180-1-sachinpb@linux.ibm.com/>*
>
> *[LTP] [PATCH v3] Hugetlb: Migrating libhugetlbfs test
> truncate_reserve_wraparound.c
> <https://lore.kernel.org/ltp/20240802061342.8540-1-geetika@linux.ibm.com/>*
>
> *[LTP] [PATCH v4] Migrating the
> libhugetlbfs/testcases/stack_grow_into_huge.c test
> <https://lore.kernel.org/ltp/20240816103317.127972-1-samir@linux.vnet.ibm.com/>
> **[LTP] [PATCH v3] Migrating the
> libhugetlbfs/testcases/truncate_sigbus_versus_oom.c test
> <https://lore.kernel.org/ltp/20240407095243.65152-1-samir@linux.vnet.ibm.com/>
> **Re: [LTP] [PATCH v2] Migrating the
> libhugetlbfs/testcases/truncate_above_4GB.c test
> <https://lore.kernel.org/ltp/7c9bf212-bbd8-4889-ade9-9798cce3a29c@linux.ibm.com/>*
>
> We would greatly appreciate any updates you could provide on when these
> might be reviewed and merged. Please let us know if there are any
> additional steps we need to take or if further modifications are required.
I will go over these as a part of the September release preparations.
Sorry I haven't had time to for a review earlier.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-09-02 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 5:55 [LTP] Acceptance Status of libhugetlbfs Patches Geetika M
2024-09-02 9:30 ` Cyril Hrubis [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=ZtWFr6OWSah0k4j0@yuki.lan \
--to=chrubis@suse.cz \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=pavithra.visweswara@ibm.com \
--cc=pavrampu@linux.ibm.com \
--cc=sachinp@linux.ibm.com \
--cc=sachinpb@linux.vnet.ibm.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