Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe]  ✓ CI.Patch_applied: success for Unit tests for rtp and GT wa/tuning
Date: Mon, 3 Apr 2023 08:08:47 +0200	[thread overview]
Message-ID: <373f5f5f-5568-58cb-bdce-5733f6cf8c7d@linux.intel.com> (raw)
In-Reply-To: <20230331151415.khx4flgdsxeldz4d@ldmartin-desk2>

On 3/31/23 17:14, Lucas De Marchi wrote:
> On Tue, Mar 21, 2023 at 10:08:34PM -0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: Unit tests for rtp and GT wa/tuning
>> URL   : https://patchwork.freedesktop.org/series/115463/
>> State : success
>>
>> == Summary ==
>>
>> === Applying kernel patches on branch 'drm-xe-next' with base: ===
>> commit 1ae4dd9e82429e075aa7121404b06ce170da5848
>> Author:     Matthew Auld <matthew.auld@intel.com>
>> AuthorDate: Tue Mar 21 11:44:07 2023 +0000
>> Commit:     Matthew Auld <matthew.auld@intel.com>
>> CommitDate: Tue Mar 21 14:03:29 2023 +0000
>>
>>    drm/xe/buddy: add compatible and intersects hooks
>>
>>    Copy this from i915. We need .compatible for vram -> vram 
>> transfers, so
>>    they don't just get nooped by ttm, if need to move something from
>>    mappable to non-mappble or vice versa. The .intersects is needed for
>>    eviction, to determine if a victim resource is worth eviction. e.g 
>> if we
>>    need mappable space there is no point in evicting a resource that has
>>    zero mappable pages.
>>
>>    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>>    Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>>    Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>    Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>
> we will probably need to change this format a little bit. Now `b4 am` is
> complaining:
>
>     ! Trailer: Commit: Matthew Auld <matthew.auld@intel.com>
>      Msg From: Patchwork <patchwork@emeril.freedesktop.org>
>     ! Trailer: Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>      Msg From: Patchwork <patchwork@emeril.freedesktop.org>
>     ! Trailer: Reviewed-by: Maarten Lankhorst 
> <maarten.lankhorst@linux.intel.com>
>      Msg From: Patchwork <patchwork@emeril.freedesktop.org>
>     ! Trailer: Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>      Msg From: Patchwork <patchwork@emeril.freedesktop.org>
>
> ( it would have been worse if it would add the r-b/a-b )


Well, b4 will complain if the format is not the one provided by:

     $ git log --pretty=email

or:

     $ git log --pretty=mboxrd


Regards,
Mauro



  reply	other threads:[~2023-04-03  6:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 22:05 [Intel-xe] [PATCH 0/7] Unit tests for rtp and GT wa/tuning Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 1/7] drm/xe: Add basic unit tests for rtp Lucas De Marchi
2023-03-27 17:56   ` Michał Winiarski
2023-03-31 13:43     ` Lucas De Marchi
2023-04-01  8:59       ` Lucas De Marchi
2023-04-01 18:54         ` Michał Winiarski
2023-04-02  1:24           ` Lucas De Marchi
2023-04-02 10:51             ` Michal Wajdeczko
2023-03-31 14:34     ` Lucas De Marchi
2023-04-01  8:54       ` Lucas De Marchi
2023-04-01 18:26         ` Michał Winiarski
2023-04-02  1:34           ` Lucas De Marchi
2023-04-02 11:17             ` Michal Wajdeczko
2023-04-02 21:54               ` Lucas De Marchi
2023-04-03  7:38                 ` Michal Wajdeczko
2023-04-03 13:02                   ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 2/7] drm/xe: Extract function to initialize xe->info Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 3/7] drm/xe: Move test infra out of xe_pci.[ch] Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 4/7] drm/xe: Use XE_KUNIT for symbol namespace Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 5/7] drm/xe: Generalize fake device creation Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 6/7] drm/xe/reg_sr: Save errors for kunit integration Lucas De Marchi
2023-03-27 18:29   ` Michał Winiarski
2023-03-31 14:43     ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 7/7] drm/xe: Add test for GT workarounds and tunings Lucas De Marchi
2023-03-21 22:08 ` [Intel-xe] ✓ CI.Patch_applied: success for Unit tests for rtp and GT wa/tuning Patchwork
2023-03-31 15:14   ` Lucas De Marchi
2023-04-03  6:08     ` Mauro Carvalho Chehab [this message]
2023-03-21 22:09 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-21 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-21 22:25 ` [Intel-xe] ○ CI.BAT: info " 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=373f5f5f-5568-58cb-bdce-5733f6cf8c7d@linux.intel.com \
    --to=mauro.chehab@linux.intel.com \
    --cc=intel-xe@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