Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"kamil.konieczny@linux.intel.com"
	<kamil.konieczny@linux.intel.com>
Cc: "Konieczny, Kamil" <kamil.konieczny@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] lib/i915: Add a helper to read mmio registers via ioctl
Date: Mon, 11 Sep 2023 16:42:49 +0000	[thread overview]
Message-ID: <cec02447c393313f14a5c3d335af2a94ab4a027b.camel@intel.com> (raw)
In-Reply-To: <20230828112309.pgkge7axxoeqhafy@kamilkon-desk.igk.intel.com>

Hi Kamil,

Apologies for the tardy response.
Thanks again for taking the time to review.
I will fix everything below as per your recommendation.
might need some trivial mods to callers.

alan:snip

I do wanna explain the below hunk specifically though, but i prefer your recommendation:
On one of my first upstream patch reviews, i was asked to re-arrange the headers of a hunk
to be alphabetical eventhough my change was just adding 1 header.
I'll fix below to add just the needed. :)

> > --- a/tools/i915-perf/i915_perf_recorder.c
> > +++ b/tools/i915-perf/i915_perf_recorder.c
> > @@ -44,14 +44,15 @@
> >  
> >  #include <i915_drm.h>
> >  
> > -#include "i915/i915_drm_local.h"
> > -
> > +#include "i915_perf_recorder_commands.h"
> 
> Why do you touch unrelated headers?
> 
> >  #include "igt_core.h"
> >  #include "intel_chipset.h"
> > +
> > +#include "i915/i915_drm_local.h"
> >  #include "i915/perf.h"
> >  #include "i915/perf_data.h"
> >  
> > -#include "i915_perf_recorder_commands.h"
> > +#include "lib/intel_reg.h"
> ------------ ^^^^^^^^^^^^^^^
> You need only this here.



      reply	other threads:[~2023-09-11 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 18:37 [igt-dev] [PATCH i-g-t v2] lib/i915: Add a helper to read mmio registers via ioctl Alan Previn
2023-08-25 18:50 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-08-25 19:11 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-08-25 19:22 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-08-26 12:52 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-08-28 11:23 ` [igt-dev] [PATCH i-g-t v2] " Kamil Konieczny
2023-09-11 16:42   ` Teres Alexis, Alan Previn [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=cec02447c393313f14a5c3d335af2a94ab4a027b.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox