Linux bluetooth development
 help / color / mirror / Atom feed
From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth: hci_bcm: remove duplicated brcm,bcm4330-bt compatible
Date: Thu, 16 Sep 2021 16:31:02 -0700	[thread overview]
Message-ID: <870dfd6edabca3e8354b099046c28e07c38a2762.camel@linux.intel.com> (raw)
In-Reply-To: <413556b2-61c6-941c-60b0-991965e41e87@canonical.com>

Hi 

On Thu, 2021-09-16 at 21:26 +0200, Krzysztof Kozlowski wrote:
> On 16/09/2021 20:06, bluez.test.bot@gmail.com wrote:
> > 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=548291
> > 
> > ---Test result---
> > 
> > Test Summary:
> > CheckPatch                    FAIL      0.44 seconds
> > GitLint                       PASS      0.10 seconds
> > BuildKernel                   PASS      519.20 seconds
> > TestRunner: Setup             PASS      345.93 seconds
> > TestRunner: l2cap-tester      PASS      2.70 seconds
> > TestRunner: bnep-tester       PASS      1.93 seconds
> > TestRunner: mgmt-tester       PASS      31.31 seconds
> > TestRunner: rfcomm-tester     PASS      2.09 seconds
> > TestRunner: sco-tester        PASS      2.12 seconds
> > TestRunner: smp-tester        PASS      2.16 seconds
> > TestRunner: userchan-tester   PASS      1.95 seconds
> > 
> > Details
> > ##############################
> > Test: CheckPatch - FAIL - 0.44 seconds
> > Run checkpatch.pl script with rule in .checkpatch.conf
> > Bluetooth: hci_bcm: remove duplicated brcm,bcm4330-bt compatible
> > WARNING: Unknown commit id '81534d4835de', maybe rebased or not pulled?
> > #9: 
> > Fixes: 81534d4835de ("Bluetooth: btbcm: Add BCM4330 and BCM4334 compatibles")
> 
> Although you asked not to reply to this email, but you also sent it to
> public mailing list, so I will reply.
> 
> Your report is incorrect. Commit ID 81534d4835de is from mainline,
> merged into Linus' tree as: v5.13-rc1~94^2~197^2~38
> 
> > total: 0 errors, 1 warnings, 7 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] Bluetooth: hci_bcm: remove duplicated brcm,bcm4330-bt" has style problems, please
> > review.
> > 
> > NOTE: If any of the errors are false positives, please report
> >       them to the maintainer, see CHECKPATCH in MAINTAINERS.
> 
> Checkpatch does not report any warnings like that, so this is false
> positive of your system, not checkpatch.
> 
It is a known issue and will be fixed soon.
Sorry for the trouble.


> 
> 
> Best regards,
> Krzysztof

Regards,
Tedd


  reply	other threads:[~2021-09-16 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 17:05 [PATCH] Bluetooth: hci_bcm: remove duplicated brcm,bcm4330-bt compatible Krzysztof Kozlowski
2021-09-16 18:06 ` bluez.test.bot
2021-09-16 19:26   ` Krzysztof Kozlowski
2021-09-16 23:31     ` Tedd Ho-Jeong An [this message]
2021-09-16 22:27 ` [PATCH] " Linus Walleij

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=870dfd6edabca3e8354b099046c28e07c38a2762.camel@linux.intel.com \
    --to=tedd.an@linux.intel.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-bluetooth@vger.kernel.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