From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Daniel Lenski <dlenski@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Bluetooth: Add a new QCA_ROME device (0cf3:e500)
Date: Tue, 18 May 2021 14:58:01 -0700 [thread overview]
Message-ID: <895354ffe5ba4a9080ea6c10e1d66ec424e74349.camel@linux.intel.com> (raw)
In-Reply-To: <CAOw_LSHKPDfRo98zLe9Luc2cY1htLyfuGGF0XE6BYsvKtBPxNA@mail.gmail.com>
Hi Dan
On Tue, 2021-05-18 at 14:41 -0700, Daniel Lenski wrote:
> Hi all,
> I'm somewhat confused about why CheckPatch is failing to approve this
> patch. It says that a commit referenced in the commit message does not
> exist:
>
> On Tue, May 18, 2021 at 12:31 PM <bluez.test.bot@gmail.com> wrote:
> > Test: CheckPatch - FAIL - 0.84 seconds
> > Run checkpatch.pl script with rule in .checkpatch.conf
> > Bluetooth: Add a new QCA_ROME device (0cf3:e500)
> > WARNING: Unknown commit id '0a03f98b98c2', maybe rebased or not pulled?
> > #9:
> > commit 0a03f98b98c2 ("Bluetooth: Add a new 04ca:3015 QCA_ROME device").
>
> However, this commit *does* exist, and it is — as far as I can tell —
> the *only* commit which exists with this text in its title.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0a03f98b98c201191e3ba15a0e33f46d8660e1fd
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?qt=grep&q=Add+a+new+04ca%3A3015+QCA_ROME+device
>
> Any suggestions about how to resolve this?
You can ignore this error.
This is an issue in the CI which is not pulling the entire kernel tree to
reduce the running time.
>
> -Dan Lenski
Regards,
Tedd
next prev parent reply other threads:[~2021-05-18 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 18:59 [PATCH] Bluetooth: Add a new QCA_ROME device (0cf3:e500) Daniel Lenski
2021-05-18 19:31 ` bluez.test.bot
2021-05-18 21:41 ` Daniel Lenski
2021-05-18 21:58 ` Tedd Ho-Jeong An [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 17:25 [PATCH] " Daniel Lenski
2021-05-18 18:37 ` bluez.test.bot
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=895354ffe5ba4a9080ea6c10e1d66ec424e74349.camel@linux.intel.com \
--to=tedd.an@linux.intel.com \
--cc=dlenski@gmail.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;
as well as URLs for NNTP newsgroup(s).