All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Christian Brauner <christian.brauner@ubuntu.com>,
	Aleksa Sarai <cyphar@cyphar.com>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>,
	shuah@kernel.org, Christian Brauner <christian@brauner.io>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: openat2: Fix testing failure for O_LARGEFILE flag
Date: Tue, 24 Aug 2021 10:50:23 -0600	[thread overview]
Message-ID: <15672b09-e4fc-78ec-7415-1ff7b777cc15@linuxfoundation.org> (raw)
In-Reply-To: <11702c81-8b7c-bbe6-705a-f0fed5f10ba5@linuxfoundation.org>

On 8/24/21 8:33 AM, Shuah Khan wrote:
> On 8/24/21 5:36 AM, Christian Brauner wrote:
>> On Tue, Aug 24, 2021 at 09:21:29PM +1000, Aleksa Sarai wrote:
>>> On 2021-08-23, Shuah Khan <skhan@linuxfoundation.org> wrote:
>>>> Hi Baolin,
>>>>
>>>> On 8/22/21 8:40 PM, Baolin Wang wrote:
>>>>> Hi Shuah,
>>>>>
>>>>> On 2021/7/28 20:32, Baolin Wang wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> When running the openat2 test suite on ARM64 platform, we got below failure,
>>>>>>> since the definition of the O_LARGEFILE is different on ARM64. So we can
>>>>>>> set the correct O_LARGEFILE definition on ARM64 to fix this issue.
>>>>>>
>>>>>> Sorry, I forgot to copy the failure log:
>>>>>>

Please send me v2 with failure log included in the commit log.

thanks,
-- Shuah


  reply	other threads:[~2021-08-24 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 12:29 [PATCH] selftests: openat2: Fix testing failure for O_LARGEFILE flag Baolin Wang
2021-07-28 12:32 ` Baolin Wang
2021-08-23  2:40   ` Baolin Wang
2021-08-23 19:23     ` Shuah Khan
2021-08-24  5:26       ` Baolin Wang
2021-08-24 11:21       ` Aleksa Sarai
2021-08-24 11:36         ` Christian Brauner
2021-08-24 14:33           ` Shuah Khan
2021-08-24 16:50             ` Shuah Khan [this message]
2021-08-25  1:49               ` Baolin Wang

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=15672b09-e4fc-78ec-7415-1ff7b777cc15@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=christian@brauner.io \
    --cc=cyphar@cyphar.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 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.