public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vasilev, Oleg" <oleg.vasilev@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v2] tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest
Date: Mon, 17 Jun 2019 10:05:29 +0000	[thread overview]
Message-ID: <df8fd2e741a6345aa48168b39e1345fe5294ccbe.camel@intel.com> (raw)
In-Reply-To: <20190614153051.GA5942@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

Hi,

Thank you for the review. I've sent an updated patch.

On Fri, 2019-06-14 at 18:30 +0300, Ville Syrjälä wrote:
> On Thu, Jun 13, 2019 at 04:06:23PM +0300, Oleg Vasilev wrote:
> > 
> > +static void format_hex_string(unsigned char edid[static
> > EDID_LENGTH],
> > +			      char buf[static EDID_LENGTH * 5 + 1])
> 
> What's the deal with those 'static's?

This enforces an array size to be at least EDID_LENGTH.

https://hamberg.no/erlend/posts/2013-02-18-static-array-indices.html

> 
> The kernel does modify the reported EDID for some quirks IIRC. I
> don't
> really like that behaviour, and it would be an issue for this test.
> But
> I guess we don't have any of those on any monitors we test.

I guess, if we see the regression like this, the test should be further
updated in order to handle those cases.

Oleg

> 
> Apart from the minor nits looks good to me.
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> 
> >  }
> >  
> >  static void setup_pc8(void)
> > -- 
> > 2.21.0

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3261 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-06-17 10:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 13:06 [igt-dev] [PATCH v2] tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest Oleg Vasilev
2019-06-13 16:14 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest (rev3) Patchwork
2019-06-14 15:30 ` [igt-dev] [PATCH v2] tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest Ville Syrjälä
2019-06-17 10:05   ` Vasilev, Oleg [this message]
2019-06-17 13:26     ` Ville Syrjälä
2019-06-17 13:40       ` Petri Latvala
2019-06-17 14:09         ` Ville Syrjälä
2019-06-17 14:22           ` Ser, Simon
2019-06-15  3:45 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest (rev3) Patchwork
2019-06-17 10:03 ` [igt-dev] [PATCH v3] tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest Oleg Vasilev
2019-06-17 13:26 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest (rev4) Patchwork
2019-06-17 18:05 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-19  8:58 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/i915_pm_rpm: improved strictness and verbosity of i2c subtest (rev3) 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=df8fd2e741a6345aa48168b39e1345fe5294ccbe.camel@intel.com \
    --to=oleg.vasilev@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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