Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t] Update MAINTAINERS
Date: Mon, 17 Oct 2022 15:24:52 +0300	[thread overview]
Message-ID: <20221017122452.2067701-1-petri.latvala@intel.com> (raw)

Add Kamil Konieczny.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Arkadiusz Hiler <arek@hiler.eu>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: Katarzyna Dec <katarzyna.dec@intel.com>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 383c327c..6bc08e39 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,2 +1,3 @@
 Petri Latvala <petri.latvala@intel.com>
 Arkadiusz Hiler <arek@hiler.eu>
+Kamil Konieczny <kamil.konieczny@linux.intel.com>
-- 
2.30.2

             reply	other threads:[~2022-10-17 12:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 12:24 Petri Latvala [this message]
2022-10-17 12:47 ` [igt-dev] ✗ GitLab.Pipeline: warning for Update MAINTAINERS Patchwork
2022-10-17 12:57 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-10-17 18:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-24 12:25 ` [igt-dev] [PATCH i-g-t] " Arkadiusz Hiler
2022-10-24 13:01 ` Kamil Konieczny
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21 13:38 Kamil Konieczny
2023-06-21 13:45 ` Petri Latvala
2023-06-21 13:55 ` Juha-Pekka Heikkila
2023-06-22 15:03 Kamil Konieczny
2023-06-23  3:09 ` Modem, Bhanuprakash
2023-06-28 17:07 Kamil Konieczny
2023-06-28 17:33 ` Juha-Pekka Heikkila
2023-06-28 18:04 ` Petri Latvala
2023-06-29  4:34 ` Modem, Bhanuprakash
2023-06-29  5:21 ` Dixit, Ashutosh

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=20221017122452.2067701-1-petri.latvala@intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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