All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: igt-dev@lists.freedesktop.org, Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] Merge patches that are failing to land in the ML and patchworks
Date: Sun, 23 Oct 2022 19:49:49 -0700	[thread overview]
Message-ID: <87sfjeorzm.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <Y1K8Nn/Gem9BCgg8@unerlige-ril>

On Fri, 21 Oct 2022 08:35:18 -0700, Umesh Nerlige Ramappa wrote:
>
> Hi Petri,
>
> Reg: [igt-dev] [PATCH i-g-t v6 00/36] Add DG2 OA test
>
> I posted this series a while ago and I have some large XML files in these
> patches that are not landing in the ML because mail servers reject
> it. Hence, it does not make it to patchworks and I am not able to run
> pre-merge CI on the kernel patches.
>
> To resolve this, I am planning to just merge the XML files and relevant
> scripts as a separate series of 10 patches shared here:
>
> https://gitlab.freedesktop.org/unerlige/igt-gpu-tools/-/commits/master
>
> Once that is merged, I will post the remaining patches to the ML so that
> pre-merge can run. I did a sanity check on these patches with kbl, tgl,
> adlp (with guc) and I don't see any issues.
>
> Requesting an Ack for this.

Because the patches and scripts are only OA related, this is:

Acked-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

Lionel,

Could you please ack again on the mailing list if possible (Lionel has
already acked privately previously).

Thanks.
--
Ashutosh

  reply	other threads:[~2022-10-24  2:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 15:35 [igt-dev] Merge patches that are failing to land in the ML and patchworks Umesh Nerlige Ramappa
2022-10-24  2:49 ` Dixit, Ashutosh [this message]
2022-10-24  8:29 ` Petri Latvala
2022-10-24 15:34 ` Dixit, Ashutosh
2022-10-24 19:48   ` Umesh Nerlige Ramappa
2022-10-25  1:32     ` 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=87sfjeorzm.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=umesh.nerlige.ramappa@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 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.