From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for linux-next: build failure after merge of the kunit-next tree
Date: Thu, 29 Feb 2024 05:10:25 -0000 [thread overview]
Message-ID: <170918342525.375736.11074172386907001188@8e613ede5ea5> (raw)
In-Reply-To: <20240229152653.09ecf771@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the kunit-next tree
URL : https://patchwork.freedesktop.org/series/130537/
State : warning
== Summary ==
Error: dim checkpatch failed
f4534e24d7e8 linux-next: build failure after merge of the kunit-next tree
-:14: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#14:
191 | "buddy_alloc failed with bias(%x-%x), size=%u, ps=%u\n",
-:41: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit c70703320e55 ("drm/tests/drm_buddy: add alloc_range_bias test")'
#41:
c70703320e55 ("drm/tests/drm_buddy: add alloc_range_bias test")
total: 1 errors, 1 warnings, 0 checks, 8 lines checked
next prev parent reply other threads:[~2024-02-29 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 4:26 linux-next: build failure after merge of the kunit-next tree Stephen Rothwell
2024-02-29 5:10 ` Patchwork [this message]
2024-02-29 5:27 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-02-29 15:07 ` Shuah Khan
2024-03-01 7:15 ` David Gow
2024-03-01 10:43 ` Stephen Rothwell
2024-03-01 16:05 ` Shuah Khan
2024-03-01 20:46 ` Stephen Rothwell
2024-03-01 22:30 ` Shuah Khan
2024-03-06 15:25 ` Shuah Khan
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=170918342525.375736.11074172386907001188@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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.