From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Priyanka Dandamudi <priyanka.dandamudi@intel.com>,
Andi Shyti <andi.shyti@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>,
Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_sysfs: Add helpers to iterate over GTs
Date: Wed, 27 Apr 2022 08:56:49 -0700 [thread overview]
Message-ID: <87k0ba5xku.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <YmkrTvxDCv840AT2@kamilkon-DESK1>
On Wed, 27 Apr 2022 04:38:54 -0700, Kamil Konieczny wrote:
>
> > +/**
> > + * igt_sysfs_gt_open:
> > + * @device: fd of the device
> > + * @gt: gt number
> > + *
> > + * This opens the sysfs gt directory corresponding to device and gt for use
> > + * with igt_sysfs_set() and igt_sysfs_get().
> > + *
> > + * Returns:
> > + * The directory fd, or -1 on failure.
> > + */
> > +int igt_sysfs_gt_open(int device, int gt)
> > +{
> > + char path[96];
> > +
> > + if (igt_debug_on(!igt_sysfs_gt_path(device, gt, path, sizeof(path))))
> ----------- ^
> imho here we should not use igt_debug_on because we use this
> function in iterator macro for_each_sysfs_gt_dirfd and the end
> condition is hitting end of available GTs and returning -1.
Hi Kamil,
You are right, I removed other igt_debug_on's and merged it but missed this
one. Somebody will need to send a patch for this. Sorry about that.
Thanks.
--
Ashutosh
prev parent reply other threads:[~2022-04-27 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 15:04 [igt-dev] [PATCH i-g-t] lib/igt_sysfs: Add helpers to iterate over GTs priyanka.dandamudi
2022-04-26 15:15 ` [igt-dev] ✗ Fi.CI.BUILD: failure for " Patchwork
2022-04-27 11:38 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2022-04-27 15:56 ` Dixit, Ashutosh [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=87k0ba5xku.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=andi.shyti@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=priyanka.dandamudi@intel.com \
--cc=sujaritha.sundaresan@intel.com \
--cc=tvrtko.ursulin@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.