linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, peter.tsao@mediatek.com
Subject: RE: MTK mt7921 driver upstream
Date: Mon, 30 Nov 2020 00:03:16 -0800 (PST)	[thread overview]
Message-ID: <5fc4a744.1c69fb81.1b7f4.4ea0@mx.google.com> (raw)
In-Reply-To: <20201130071655.31515-1-peter.tsao@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=393043

---Test result---

##############################
Test: CheckPatch - FAIL
Output:
MTK mt7921 driver upstream
WARNING: Missing commit description - Add an appropriate one

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#9: 
new file mode 100644

total: 0 errors, 2 warnings, 12491 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

"[PATCH] MTK mt7921 driver upstream" has style problems, please review.

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: CheckGitLint - PASS

##############################
Test: CheckBuildK - PASS



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2020-11-30  8:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  7:16 [PATCH] MTK mt7921 driver upstream peter.tsao
2020-11-30  7:31 ` bluez.test.bot
2020-11-30  8:03 ` bluez.test.bot [this message]
2020-11-30 17:03 ` [PATCH] " Marcel Holtmann

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=5fc4a744.1c69fb81.1b7f4.4ea0@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=peter.tsao@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).