From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Anshuman Gupta" <anshuman.gupta@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for DGFX OpRegion (rev4)
Date: Mon, 18 Apr 2022 11:41:46 -0000 [thread overview]
Message-ID: <165028210627.11401.7259040339151067549@emeril.freedesktop.org> (raw)
In-Reply-To: <20220418105408.13444-1-anshuman.gupta@intel.com>
== Series Details ==
Series: DGFX OpRegion (rev4)
URL : https://patchwork.freedesktop.org/series/99738/
State : warning
== Summary ==
Error: dim checkpatch failed
f20709da5fa0 drm/i915/opregion: Add intel_opregion_init() wrapper
78a0ce03f189 drm/i915/opregion: Abstract opregion function
69eb07b28866 drm/i915/opregion: Add dgfx opregion func
6268b7ad8dd7 drm/i915/opregion: Cond dgfx opregion func registration
9cbb10bdb056 drm/i915/dgfx: OPROM OpRegion Setup
-:236: CHECK:ALLOC_SIZEOF_STRUCT: Prefer kzalloc(sizeof(*exprom_hdr)...) over kzalloc(sizeof(struct expansion_rom_header)...)
#236: FILE: drivers/gpu/drm/i915/display/intel_opregion.c:1046:
+ exprom_hdr = kzalloc(sizeof(struct expansion_rom_header), GFP_KERNEL);
-:237: CHECK:ALLOC_SIZEOF_STRUCT: Prefer kzalloc(sizeof(*exprom_pci_data)...) over kzalloc(sizeof(struct pci_data_structure)...)
#237: FILE: drivers/gpu/drm/i915/display/intel_opregion.c:1047:
+ exprom_pci_data = kzalloc(sizeof(struct pci_data_structure), GFP_KERNEL);
total: 0 errors, 0 warnings, 2 checks, 395 lines checked
bcbd63a312ee drm/i915/dgfx: Get VBT from rvda
next prev parent reply other threads:[~2022-04-18 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 10:54 [Intel-gfx] [PATCH v4 0/6] DGFX OpRegion Anshuman Gupta
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 1/6] drm/i915/opregion: Add intel_opregion_init() wrapper Anshuman Gupta
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 2/6] drm/i915/opregion: Abstract opregion function Anshuman Gupta
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 3/6] drm/i915/opregion: Add dgfx opregion func Anshuman Gupta
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 4/6] drm/i915/opregion: Cond dgfx opregion func registration Anshuman Gupta
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 5/6] drm/i915/dgfx: OPROM OpRegion Setup Anshuman Gupta
2022-04-18 14:49 ` kernel test robot
2022-04-18 10:54 ` [Intel-gfx] [PATCH v4 6/6] drm/i915/dgfx: Get VBT from rvda Anshuman Gupta
2022-04-18 11:41 ` Patchwork [this message]
2022-04-18 11:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for DGFX OpRegion (rev4) Patchwork
2022-04-18 12:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-18 13:29 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=165028210627.11401.7259040339151067549@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@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.