linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: Fix test result reporting in gup_longterm
Date: Thu, 15 May 2025 15:13:40 +0530	[thread overview]
Message-ID: <a5554b6e-0db0-4f34-b42a-b0b0b9a047bc@arm.com> (raw)
In-Reply-To: <aCW2z7xlQk2iyEP9@finisterre.sirena.org.uk>



On 15/05/25 3:11 pm, Mark Brown wrote:
> On Thu, May 15, 2025 at 03:05:07PM +0530, Dev Jain wrote:
>> On 15/05/25 2:27 pm, Mark Brown wrote:
> 
>>> @@ -189,7 +214,10 @@ static void do_test(int fd, size_t size, enum test_type type, bool shared)
>>>    		 * some previously unsupported filesystems, we might want to
>>>    		 * perform some additional tests for possible data corruptions.
>>>    		 */
>>> -		ksft_test_result(should_work, "Should have worked\n");
>>> +		if (should_work)
>>> +			result = KSFT_PASS;
> 
>> Missed printing "Should have worked" here.
> 
> I didn't think that output was particularly useful separate to the
> overall test result (which is logged on exit from the function), it's
> just the test result more than diagnostic information.

No hard opinion.

> 
> Please delete unneeded context from mails when replying.  Doing this
> makes it much easier to find your reply in the message, helping ensure
> it won't be missed by people scrolling through the irrelevant quoted
> material.

You have mentioned that before, sorry my bad! I also hate it :)



  reply	other threads:[~2025-05-15  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15  8:57 Mark Brown
2025-05-15  9:35 ` Dev Jain
2025-05-15  9:41   ` Mark Brown
2025-05-15  9:43     ` Dev Jain [this message]
2025-05-16  8:02 ` David Hildenbrand
2025-05-16 12:29   ` Mark Brown
2025-05-16 12:55     ` David Hildenbrand
2025-05-16 13:09       ` Mark Brown
2025-05-16 14:12         ` David Hildenbrand
2025-05-16 18:07           ` Mark Brown
2025-05-19 13:28             ` David Hildenbrand
2025-05-19 14:55               ` Mark Brown
2025-05-21 18:48               ` Mark Brown
2025-05-22  8:42                 ` David Hildenbrand
2025-05-22  9:23                   ` Mark Brown

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=a5554b6e-0db0-4f34-b42a-b0b0b9a047bc@arm.com \
    --to=dev.jain@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.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