From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [PATCH i-g-t 2/2] tests/intel/xe_oa: Tests for OA syncs
Date: Wed, 30 Oct 2024 19:11:11 -0700 [thread overview]
Message-ID: <85wmhpxbr4.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20241030125411.cocpywc7o4yigob5@kamilkon-desk.igk.intel.com>
On Wed, 30 Oct 2024 05:54:11 -0700, Kamil Konieczny wrote:
>
> > diff --git a/lib/xe/xe_oa.c b/lib/xe/xe_oa.c
> > index 4fdd0b8c95..c168669c5d 100644
> > --- a/lib/xe/xe_oa.c
> > +++ b/lib/xe/xe_oa.c
> > @@ -1025,8 +1025,8 @@ const char *intel_xe_perf_read_report_reason(const struct intel_xe_perf *perf,
> > return "unknown";
> > }
> >
>
> Please describe public lib function here.
Done. I also went ahead and merged this series. Thanks.
next prev parent reply other threads:[~2024-10-31 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 2:53 [PATCH i-g-t v5 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-30 2:53 ` [PATCH i-g-t 1/2] drm-uapi/xe: Sync with OA syncs uapi update Ashutosh Dixit
2024-10-30 2:53 ` [PATCH i-g-t 2/2] tests/intel/xe_oa: Tests for OA syncs Ashutosh Dixit
2024-10-30 12:54 ` Kamil Konieczny
2024-10-31 2:11 ` Dixit, Ashutosh [this message]
2024-10-30 4:07 ` ✗ Fi.CI.BAT: failure for tests/intel/oa: Tests for OA syncs (rev5) Patchwork
2024-10-30 4:07 ` ✓ CI.xeBAT: success " Patchwork
2024-10-30 8:06 ` ✗ CI.xeFULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 18:52 [PATCH i-g-t 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-25 18:52 ` [PATCH i-g-t 2/2] tests/intel/xe_oa: " Ashutosh Dixit
2024-10-25 19:35 ` Umesh Nerlige Ramappa
2024-10-25 19:45 ` 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=85wmhpxbr4.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.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.