From: Shuah Khan <skhan@linuxfoundation.org>
To: Jun Miao <jun.miao@windriver.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [V3][PATCH] selftests/x86: Fix error: variably modified 'altstack_data' at file scope
Date: Thu, 2 Sep 2021 15:05:30 -0600 [thread overview]
Message-ID: <c21053a0-c3bb-4cda-4f16-24427dd5b0ff@linuxfoundation.org> (raw)
In-Reply-To: <09fb52ee-3041-991a-0277-ff01eef2643f@windriver.com>
On 9/2/21 2:45 AM, Jun Miao wrote:
> Hi all,
>
> What about this patch?
>
> Thanks
> Jun
>
>
> On 8/24/21 10:43 AM, Jun Miao wrote:
>> Based on glibc 2.33 -> 2.34, there is one new feature:
>>
Please don't top post.
It is applied to linux-kselftest next for Linux 5.15-rc1
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=next
thanks,
-- Shuah
prev parent reply other threads:[~2021-09-02 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 2:43 [V3][PATCH] selftests/x86: Fix error: variably modified 'altstack_data' at file scope Jun Miao
2021-09-02 8:45 ` Jun Miao
2021-09-02 21:05 ` Shuah Khan [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=c21053a0-c3bb-4cda-4f16-24427dd5b0ff@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jun.miao@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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