public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org,
	Swati Sharma <swati2.sharma@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 5/5] lib/igt_fb: add missing include in header
Date: Mon, 23 Jan 2023 12:37:07 +0200	[thread overview]
Message-ID: <Y85jU+LmXJ+P+on1@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20230120181243.oysvrqxat3vs7gzh@kamilkon-desk1>

On Fri, Jan 20, 2023 at 07:12:43PM +0100, Kamil Konieczny wrote:
> Petri: there is also no [igt-dev] in subject ?
> 

Because you received the mail by Cc. [igt-dev] is added by the mailing
list, it's never added by hand.


-- 
Petri Latvala

  parent reply	other threads:[~2023-01-23 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 17:41 [igt-dev] [PATCH i-g-t 0/5] tests/i915/kms_dsc: Reorg + Fix Swati Sharma
2023-01-20 17:41 ` [igt-dev] [PATCH i-g-t 1/5] lib/dsc: Move VDSC functions to separate lib file Swati Sharma
2023-01-20 17:41 ` [igt-dev] [PATCH i-g-t 2/5] Move wrapper functions from kms_dsc to kms_dsc_helper Swati Sharma
2023-01-20 17:41 ` [igt-dev] [PATCH i-g-t 3/5] tests/i915/kms_dsc: Add disp_ver as struct data_t member Swati Sharma
2023-01-20 17:41 ` [igt-dev] [PATCH i-g-t 4/5] tests/i915/kms_dsc_helper: Improve format string Swati Sharma
2023-01-20 17:41 ` [igt-dev] [PATCH i-g-t 5/5] lib/igt_fb: add missing include in header Swati Sharma
2023-01-20 18:12   ` Kamil Konieczny
2023-01-21  5:28     ` Swati Sharma
2023-01-23 10:37     ` Petri Latvala [this message]
2023-01-20 18:58 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/kms_dsc: Reorg + Fix Patchwork
2023-01-21 20:10 ` [igt-dev] ✓ Fi.CI.IGT: " 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=Y85jU+LmXJ+P+on1@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=swati2.sharma@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