Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: "Samala, Pranay" <pranay.samala@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v1 1/2] tests/kms_scaling_modes: Add informative messages for skipped scaling mode tests
Date: Thu, 5 Dec 2024 20:32:47 +0530	[thread overview]
Message-ID: <e06beb5f-1997-4cb0-a087-c48e6541a6cf@intel.com> (raw)
In-Reply-To: <PH7PR11MB6053BE56088EC9B654006706E7302@PH7PR11MB6053.namprd11.prod.outlook.com>

Hi Pranay,

Thanks for the review.

On 12/5/2024 8:20 PM, Samala, Pranay wrote:
> Hi Ramanaidu,
>
>> -----Original Message-----
>> From: Naladala, Ramanaidu <ramanaidu.naladala@intel.com>
>> Sent: Thursday, December 5, 2024 5:55 PM
>> To: igt-dev@lists.freedesktop.org
>> Cc: Samala, Pranay <pranay.samala@intel.com>; Naladala, Ramanaidu
>> <ramanaidu.naladala@intel.com>
>> Subject: [PATCH i-g-t v1 1/2] tests/kms_scaling_modes: Add informative
>> messages for skipped scaling mode tests
>>
>> Add `igt_info` messages to provide more context when skipping outputs that do
>> not support scaling mode. Include `igt_info` messages to indicate when invalid
>> pipe/output combinations are skipped.
>>
>> V1: Fix alignment issues. (Pranay)
>>
>> Signed-off-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>
>> ---
>>   tests/kms_scaling_modes.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/kms_scaling_modes.c b/tests/kms_scaling_modes.c index
>> 5fd34c4b2..e8aeb7409 100644
>> --- a/tests/kms_scaling_modes.c
>> +++ b/tests/kms_scaling_modes.c
>> @@ -117,8 +117,11 @@ static void test_scaling_mode(data_t *data, uint32_t
>> flags)
>>   	for_each_pipe_with_valid_output(display, pipe, output) {
>>   		igt_display_reset(display);
>>
>> -		if (!has_scaling_mode(output))
>> +		if (!has_scaling_mode(output)) {
>> +			igt_info("Output %s does not support scaling mode.\n",
>> +				igt_output_name(output));
> Alignment should match open parenthesis
> i of igt should come below "
This alignment issue will be fix during merging. Since it's a 
non-functional fix, there's no need to go through the CI cycle again.
>
> With this fixed, code LGTM.
> Reviewed-by: Pranay Samala <pranay.samala@intel.com>
>>   			continue;
>> +		}
>>
>>   		igt_output_set_pipe(output, pipe);
>>   		if (!intel_pipe_output_combo_valid(display))
>> --
>> 2.43.0

  reply	other threads:[~2024-12-05 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 12:25 [PATCH i-g-t v1 0/2] Update skip messages in scaling modes Naladala Ramanaidu
2024-12-05 12:25 ` [PATCH i-g-t v1 1/2] tests/kms_scaling_modes: Add informative messages for skipped scaling mode tests Naladala Ramanaidu
2024-12-05 14:50   ` Samala, Pranay
2024-12-05 15:02     ` Naladala, Ramanaidu [this message]
2024-12-05 12:25 ` [PATCH i-g-t v1 2/2] HAX patch do not merge Naladala Ramanaidu
2024-12-06  2:32 ` ✓ i915.CI.BAT: success for Update skip messages in scaling modes (rev2) Patchwork
2024-12-06  3:21 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-06  4:08 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-06  5:58 ` ✗ Xe.CI.Full: " Patchwork

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=e06beb5f-1997-4cb0-a087-c48e6541a6cf@intel.com \
    --to=ramanaidu.naladala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=pranay.samala@intel.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