From: Jani Nikula <jani.nikula@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH i-g-t 0/4] tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel
Date: Mon, 11 Aug 2025 15:50:22 +0300 [thread overview]
Message-ID: <cover.1754916577.git.jani.nikula@intel.com> (raw)
Sync intel_vbt_defs.h from kernel commit by commit.
Jani Nikula (4):
tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit
bc3ca4d94369
tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit
70c33a2710cd
tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit
dac2ec8d3ba2
tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit
96b451d53ae9
tools/intel_bios.h | 8 -------
tools/intel_vbt_decode.c | 12 +++++-----
tools/intel_vbt_defs.h | 51 +++++++++++++++++++++++++++++++++-------
3 files changed, 48 insertions(+), 23 deletions(-)
--
2.47.2
next reply other threads:[~2025-08-11 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:50 Jani Nikula [this message]
2025-08-11 12:50 ` [PATCH i-g-t 1/4] tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit bc3ca4d94369 Jani Nikula
2025-08-13 13:59 ` Kamil Konieczny
2025-08-11 12:50 ` [PATCH i-g-t 2/4] tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit 70c33a2710cd Jani Nikula
2025-08-13 14:05 ` Kamil Konieczny
2025-08-11 12:50 ` [PATCH i-g-t 3/4] tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit dac2ec8d3ba2 Jani Nikula
2025-08-13 14:12 ` Kamil Konieczny
2025-08-11 12:50 ` [PATCH i-g-t 4/4] tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel commit 96b451d53ae9 Jani Nikula
2025-08-13 14:15 ` Kamil Konieczny
2025-08-14 9:43 ` Jani Nikula
2025-08-11 15:09 ` ✗ i915.CI.BAT: failure for tools/intel_vbt_decode: sync intel_vbt_defs.h with kernel Patchwork
2025-08-11 15:35 ` ✓ Xe.CI.BAT: success " Patchwork
2025-08-11 17:14 ` ✗ Xe.CI.Full: failure " 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=cover.1754916577.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@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 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.