From: Jani Nikula <jani.nikula@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>
Subject: Re: [PATCH i-g-t] lib: sync PCI ID macros with kernel
Date: Wed, 13 Nov 2024 11:01:45 +0200 [thread overview]
Message-ID: <87plmzbj7q.fsf@intel.com> (raw)
In-Reply-To: <20241113064849.udg2ey5bglp35eyf@zkempczy-mobl2>
On Wed, 13 Nov 2024, Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> wrote:
> On Tue, Nov 12, 2024 at 03:02:10PM +0200, Jani Nikula wrote:
>
> <cut>
>
>> >
>> > I see no __KERNEL__ in current xe_pciids.h and i915_pciids.h so
>> > there's some change from my perspective. intel_vbt_defs.h also
>> > doesn't contain any kernel conditional inside. I think author
>> > of this change should provide additional documentation about this
>> > (not me) - commit message for me is not enough. Till this change
>> > I haven't noticed any __KERNEL__ usage in igt codebase and I think
>> > if it appears it should be documented what's for dead code is
>> > imported to the project.
>>
>> See igt commit e966143f5c5f ("lib/intel_device_info: use dedicated macro
>> for struct pci_id_match init"). INTEL_VGA_DEVICE has been unused in igt
>> since then.
>>
>> I wrapped the macro in #ifdef __KERNEL__ in kernel commit fc9cb46bdca8
>> ("drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE()")
>> to avoid it being used in igt again.
>
> Rationale of your change is clear to me - isolation of INTEL_VGA_DEVICE()
> to use in the kernel only. My problems are when I see such thing in the
> igt header
>
> #ifdef __KERNEL__
>
> ... some definitions ...
>
> #endif
>
> 1. is someone really is setting up __KERNEL__ in igt build system?
> What's for it is here? (cognitive problem)
> 2. this conditional is not necessary here, let's remove it.
> (dead code problem)
>
> I guess you will not accept change in which I would remove __KERNEL__
> conditional from the header (2).
>
>>
>> I'm not going to document this further in igt.
>
> I'm asking for the documenting of this change not for me, but for
> other developers who might be confused by this conditional in the
> future. Especially we want to copy this header from the kernel.
> If you still think this is not necessary I have no other arguments
> to convince you to add some note to README.md.
I didn't say it's not necessary (nor did I say that it is). I said I
decline to write further documentation on this. If igt developers want
more documentation, they know what it needs to say, and I don't.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-13 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:58 [PATCH i-g-t] lib: sync PCI ID macros with kernel Ngai-Mint Kwan
2024-11-06 20:11 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-11-06 20:12 ` ✓ CI.xeBAT: " Patchwork
2024-11-06 23:49 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-13 14:02 ` Kamil Konieczny
2024-11-07 9:34 ` [PATCH i-g-t] " Jani Nikula
2024-11-07 17:31 ` Ngai-Mint Kwan
2024-11-07 17:08 ` Kamil Konieczny
2024-11-07 18:24 ` Ngai-Mint Kwan
2024-11-07 20:49 ` Jani Nikula
2024-11-12 11:09 ` Zbigniew Kempczyński
2024-11-12 11:22 ` Jani Nikula
2024-11-12 11:57 ` Zbigniew Kempczyński
2024-11-12 13:02 ` Jani Nikula
2024-11-13 6:48 ` Zbigniew Kempczyński
2024-11-13 9:01 ` Jani Nikula [this message]
2024-11-08 2:39 ` ✗ CI.xeFULL: failure for " 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=87plmzbj7q.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=ngai-mint.kwan@linux.intel.com \
--cc=zbigniew.kempczynski@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.