From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org, juha-pekka.heikkila@intel.com,
katarzyna.piecielska@intel.com, ryszard.knop@intel.com,
ewelina.musial@intel.com, adrinael@adrinael.net,
mateusz.grabski@intel.com, konrad.b.brodzik@intel.com
Subject: Re: [PATCH i-g-t] Bump aborting on network failure deadline to 40 seconds
Date: Fri, 14 Feb 2025 10:26:24 +0100 [thread overview]
Message-ID: <e952ae21-08b6-401b-96dc-f13933f5d8a2@linux.intel.com> (raw)
In-Reply-To: <20250213133744.ilaasvjp5m7ykddx@kamilkon-desk.igk.intel.com>
On 13.02.2025 14:37, Kamil Konieczny wrote:
> Hi Peter,
> On 2025-02-12 at 16:38:34 +0100, Peter Senna Tschudin wrote:
>>
>
> One nit I forgot to add, in subject there should be 'runner: '
> prefix, just like in commit you cite in beginning.
Sorry about that. Even the patch I reference in the commit message has
the runner: prefix. My bad.
>
> In conclusion, are you ok with me aditing 2nd paragraph, dropping
> 4th paragraph where you wrote about internal-upstream CI,
> dropping 'internal' word plus adding 'runner: ' prefix in subject?
> If yes I could merge it.
Sure, looks good to me. Please mind that I refer to internal three
times one time on the original second, third, and fourth paragraphs.
Feel free to adjust the commit message as needed.
>
> Regards,
> Kamil
[...]
prev parent reply other threads:[~2025-02-14 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 15:21 [PATCH i-g-t] Bump aborting on network failure deadline to 40 seconds Peter Senna Tschudin
2025-02-06 21:06 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-02-07 2:00 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-07 7:51 ` Peter Senna Tschudin
2025-02-07 8:13 ` Ravali, JupallyX
2025-02-07 14:00 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-07 14:07 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-07 14:43 ` Peter Senna Tschudin
2025-02-10 5:35 ` Ravali, JupallyX
2025-02-07 21:01 ` ✓ Xe.CI.Full: success " Patchwork
2025-02-10 5:33 ` ✓ i915.CI.BAT: " Patchwork
2025-02-10 7:08 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-10 8:26 ` Peter Senna Tschudin
2025-02-10 14:43 ` Ravali, JupallyX
2025-02-10 10:36 ` ✓ i915.CI.Full: success " Patchwork
2025-02-11 9:21 ` [PATCH i-g-t] " Kamil Konieczny
2025-02-11 9:55 ` Peter Senna Tschudin
2025-02-11 11:59 ` Piecielska, Katarzyna
2025-02-11 13:38 ` Peter Senna Tschudin
2025-02-12 10:06 ` Knop, Ryszard
2025-02-12 13:52 ` Kamil Konieczny
2025-02-12 14:31 ` Knop, Ryszard
2025-02-12 14:59 ` Kamil Konieczny
2025-02-12 15:38 ` Peter Senna Tschudin
2025-02-13 13:37 ` Kamil Konieczny
2025-02-14 9:26 ` Peter Senna Tschudin [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=e952ae21-08b6-401b-96dc-f13933f5d8a2@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=adrinael@adrinael.net \
--cc=ewelina.musial@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=konrad.b.brodzik@intel.com \
--cc=mateusz.grabski@intel.com \
--cc=ryszard.knop@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