Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Alexander Usyskin" <alexander.usyskin@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for mtd: add driver for Intel discrete graphics (rev2)
Date: Thu, 24 Apr 2025 17:52:56 -0000	[thread overview]
Message-ID: <174551717699.7653.15286649740426260158@c664b1dc75d1> (raw)
In-Reply-To: <20250424132536.3043825-1-alexander.usyskin@intel.com>

== Series Details ==

Series: mtd: add driver for Intel discrete graphics (rev2)
URL   : https://patchwork.freedesktop.org/series/147661/
State : warning

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
202708c00696422fd217223bb679a353a5936e23
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1be8150b080b51a2ae3c731f56a8cf400925e7a4
Author: Reuven Abliyev <reuven.abliyev@intel.com>
Date:   Thu Apr 24 16:25:36 2025 +0300

    drm/xe/nvm: add support for non-posted erase
    
    Erase command is slow on discrete graphics storage
    and may overshot PCI completion timeout.
    BMG introduces the ability to have non-posted erase.
    Add driver support for non-posted erase with polling
    for erase completion.
    
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Signed-off-by: Reuven Abliyev <reuven.abliyev@intel.com>
    Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
+ /mt/dim checkpatch 6176f71822602f52bc4327965090275c5570ed0d drm-intel
9868ab101a5d mtd: core: always create master device
3f906f751f37 mtd: add driver for intel graphics non-volatile memory device
-:69: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#69: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 202 lines checked
895118fd05cd mtd: intel-dg: implement region enumeration
81d8c954dc68 mtd: intel-dg: implement access functions
f3117e5d6a36 mtd: intel-dg: register with mtd
7923307064e8 mtd: intel-dg: align 64bit read and write
70cec8e48a48 mtd: intel-dg: wake card on operations
bccb87d3baf8 drm/i915/nvm: add nvm device for discrete graphics
-:97: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#97: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 163 lines checked
eb7fb860f443 drm/i915/nvm: add support for access mode
ab2781b43716 drm/xe/nvm: add on-die non-volatile memory device
-:88: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#88: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 212 lines checked
8c46d887a2cd drm/xe/nvm: add support for access mode
1be8150b080b drm/xe/nvm: add support for non-posted erase
-:124: WARNING:MSLEEP: msleep < 20ms can sleep for up to 20ms; see function description of msleep().
#124: FILE: drivers/mtd/devices/mtd_intel_dg.c:393:
+				msleep(10);

total: 0 errors, 1 warnings, 0 checks, 150 lines checked



  parent reply	other threads:[~2025-04-24 17:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 13:25 [PATCH v9 00/12] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 01/12] mtd: core: always create master device Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 02/12] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-04-29  9:31   ` Raag Jadav
2025-05-15 10:11     ` Usyskin, Alexander
2025-05-15 12:13       ` Raag Jadav
2025-04-24 13:25 ` [PATCH v9 03/12] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-04-29  9:44   ` Raag Jadav
2025-05-15 11:23     ` Usyskin, Alexander
2025-05-15 12:19       ` Raag Jadav
2025-05-15 13:07         ` Usyskin, Alexander
2025-04-24 13:25 ` [PATCH v9 04/12] mtd: intel-dg: implement access functions Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 05/12] mtd: intel-dg: register with mtd Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 06/12] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 07/12] mtd: intel-dg: wake card on operations Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 08/12] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 09/12] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 10/12] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 11/12] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-04-24 13:25 ` [PATCH v9 12/12] drm/xe/nvm: add support for non-posted erase Alexander Usyskin
2025-04-24 17:52 ` ✓ CI.Patch_applied: success for mtd: add driver for Intel discrete graphics (rev2) Patchwork
2025-04-24 17:52 ` Patchwork [this message]
2025-04-24 17:54 ` ✓ CI.KUnit: " Patchwork
2025-04-24 18:02 ` ✓ CI.Build: " Patchwork
2025-04-24 18:04 ` ✗ CI.Hooks: failure " Patchwork
2025-04-24 18:06 ` ✗ CI.checksparse: warning " Patchwork
2025-04-24 18:30 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-25 15:25 ` ✗ 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=174551717699.7653.15286649740426260158@c664b1dc75d1 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=alexander.usyskin@intel.com \
    --cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox