From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: igt-dev@lists.freedesktop.org, quic_aravindh@quicinc.com,
petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v6 3/3] tests/kms_writeback: Enhance kms_writeback for custom modes
Date: Mon, 08 Aug 2022 12:49:07 -0700 [thread overview]
Message-ID: <85pmha8qj0.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <b8fd14ff-681b-df11-ae6b-c9b859142571@quicinc.com>
On Mon, 08 Aug 2022 10:41:50 -0700, Abhinav Kumar wrote:
>
> Hi Ashutosh
>
> On 8/8/2022 10:38 AM, Dixit, Ashutosh wrote:
> > On Thu, 04 Aug 2022 15:02:35 -0700, Rohith Iyer wrote:
> >>
> >> igt_subtest("writeback-pixel-formats") {
> >> + igt_skip_on(data.dump_check || data.list_modes);
> >> drmModePropertyBlobRes *formats_blob = get_writeback_formats_blob(output);
> >> const char *valid_chars = "01234568 ABCGNRUVXY";
> >> unsigned int i;
> >
> > $ ninja -C build
> > ninja: Entering directory `build'
> > [120/1183] Compiling C object tests/kms_writeback.p/kms_writeback.c.o
> > ../tests/kms_writeback.c: In function ‘__igt_unique____real_main480’:
> > ../tests/kms_writeback.c:532:17: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
> > 532 | drmModePropertyBlobRes *formats_blob = get_writeback_formats_blob(output);
> > | ^~~~~~~~~~~~~~~~~~~~~~
> > ../tests/kms_writeback.c:555:17: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
> > 555 | igt_fb_t invalid_output_fb;
> > | ^~~~~~~~
> > ../tests/kms_writeback.c:571:17: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
> > 571 | igt_fb_t output_fb;
> > | ^~~~~~~~
> > ../tests/kms_writeback.c:586:17: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
> > 586 | igt_fb_t output_fb;
> > | ^~~~~~~~
>
> All these warnings were pre-existing warnings in kms_writeback even before
> this series and not introduced by this series.
Hi Abhinav, doesn't seem to be the case, git blame:
531 22fa5ae83a885 (Rohith Iyer 2022-08-04 15:02:35 -0700 531) igt_skip_on(data.dump_check || data.list
> However, we will be happy to fix these for the benefit of all.
Thanks, yes please fix.
next prev parent reply other threads:[~2022-08-08 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 22:02 [igt-dev] [PATCH i-g-t v6 0/3] kms_writeback enhancements Rohith Iyer
2022-08-04 22:02 ` [igt-dev] [PATCH i-g-t v6 1/3] lib/igt_kms: Add helper to parse mode string Rohith Iyer
2022-08-04 22:02 ` [igt-dev] [PATCH i-g-t v6 2/3] tests/testdisplay: Use igt_parse_mode_string for command line arguments Rohith Iyer
2022-08-04 22:02 ` [igt-dev] [PATCH i-g-t v6 3/3] tests/kms_writeback: Enhance kms_writeback for custom modes Rohith Iyer
2022-08-04 23:06 ` Abhinav Kumar
2022-08-08 17:38 ` Dixit, Ashutosh
2022-08-08 17:41 ` Abhinav Kumar
2022-08-08 19:49 ` Dixit, Ashutosh [this message]
2022-08-08 19:59 ` Abhinav Kumar
2022-08-04 23:04 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_writeback enhancements (rev6) Patchwork
2022-08-05 4:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-08-08 16:32 ` [igt-dev] [PATCH i-g-t v6 0/3] kms_writeback enhancements Jessica Zhang
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=85pmha8qj0.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_aravindh@quicinc.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 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.