From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 1/4] lib/kms: Introduce struct igt_forced_connector
Date: Sun, 14 Apr 2024 11:25:39 +0530 [thread overview]
Message-ID: <1aa480ba-d430-448f-91fa-71c9217627b3@intel.com> (raw)
In-Reply-To: <20240411183450.6417-1-ville.syrjala@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
On 4/12/2024 12:04 AM, Ville Syrjala wrote:
> From: Ville Syrjälä<ville.syrjala@linux.intel.com>
>
> Give the forced_connector[] struct a proper type name,
> and utilize it in various places to make the code
> less messy.
>
> Cc: Kunal Joshi<kunal1.joshi@intel.com>
> Signed-off-by: Ville Syrjälä<ville.syrjala@linux.intel.com>
LGTM
Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
[-- Attachment #2: Type: text/html, Size: 1290 bytes --]
prev parent reply other threads:[~2024-04-14 5:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 18:34 [PATCH i-g-t v2 1/4] lib/kms: Introduce struct igt_forced_connector Ville Syrjala
2024-04-11 18:34 ` [PATCH i-g-t v2 2/4] lib/kms: Adjust forced_connectors[] traversal Ville Syrjala
2024-04-14 5:56 ` Joshi, Kunal1
2024-04-11 18:34 ` [PATCH i-g-t v2 3/4] lib/kms: Generalize forced_connectors[] to handle arbitrary attributes Ville Syrjala
2024-04-14 5:57 ` Joshi, Kunal1
2024-04-11 18:34 ` [PATCH i-g-t v2 4/4] lib/kms: Clear connector_attrs[] upon setting the reset value Ville Syrjala
2024-04-14 5:59 ` Joshi, Kunal1
2024-04-16 12:33 ` Ville Syrjälä
2024-04-11 19:17 ` ✓ CI.xeBAT: success for series starting with [i-g-t,v2,1/4] lib/kms: Introduce struct igt_forced_connector Patchwork
2024-04-11 19:26 ` ✓ Fi.CI.BAT: " Patchwork
2024-04-12 1:49 ` ✗ CI.xeFULL: failure " Patchwork
2024-04-12 5:17 ` ✗ Fi.CI.IGT: " Patchwork
2024-04-14 5:55 ` Joshi, Kunal1 [this message]
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=1aa480ba-d430-448f-91fa-71c9217627b3@intel.com \
--to=kunal1.joshi@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