public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Xi Ruoyao <xry111@xry111.site>,
	mengqinggang <mengqinggang@loongson.cn>,
	libc-alpha@sourceware.org
Cc: xuchenghua@loongson.cn, caiyinyu@loongson.cn,
	chenglulu@loongson.cn, cailulu@loongson.cn, i.swmail@xen0n.name,
	maskray@google.com, luweining@loongson.cn, wanglei@loongson.cn,
	hejinyang@loongson.cn, hjl.tools@gmail.com
Subject: Re: [PATCH v3] LoongArch: Add support for TLS Descriptors
Date: Thu, 14 Mar 2024 10:47:36 -0300	[thread overview]
Message-ID: <293d16ae-51ed-4e71-a750-09530cc2d149@linaro.org> (raw)
In-Reply-To: <f162f1a1c891d77023cd846936032d0cd40550e4.camel@xry111.site>



On 14/03/24 04:29, Xi Ruoyao wrote:
> On Wed, 2024-03-13 at 15:14 -0300, Adhemerval Zanella Netto wrote:
>>> There are two failures which seem unrelated though:
>>>
>>> FAIL: misc/tst-preadvwritev64v2
>>> FAIL: misc/tst-preadvwritev2
>>
>> Is this loongarch related or does it happen on any architecture?
> 
> Also on x86-64 with mainline kernel.
> 
> The failure is:
> 
> error: tst-preadvwritev2-common.c:113: preadv2 did not fail with an
> invalid flag
> 
> The "invalid flag" is calculated to 0x20, which is recently introduced
> as RWF_NOAPPEND in the kernel:
> https://lore.kernel.org/all/20240119191053.GT22081@brightrain.aerifal.cx/
> 

Right, I check this out and update the test.

      reply	other threads:[~2024-03-14 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  7:43 mengqinggang
2024-03-13 17:28 ` Xi Ruoyao
2024-03-13 18:14   ` Adhemerval Zanella Netto
2024-03-14  7:29     ` Xi Ruoyao
2024-03-14 13:47       ` Adhemerval Zanella Netto [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=293d16ae-51ed-4e71-a750-09530cc2d149@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=cailulu@loongson.cn \
    --cc=caiyinyu@loongson.cn \
    --cc=chenglulu@loongson.cn \
    --cc=hejinyang@loongson.cn \
    --cc=hjl.tools@gmail.com \
    --cc=i.swmail@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    --cc=luweining@loongson.cn \
    --cc=maskray@google.com \
    --cc=mengqinggang@loongson.cn \
    --cc=wanglei@loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).