From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>, "An, Tedd" <tedd.an@intel.com>
Subject: Re: Bluetooth: sco: prevent information leak in sco_conn_defer_accept()
Date: Fri, 25 Jun 2021 13:33:23 -0700 [thread overview]
Message-ID: <CABBYNZJoP5_d-K1hUt+G3N3KhgXoaokFRu_FQrrbYKctAqFhrg@mail.gmail.com> (raw)
In-Reply-To: <20210625195924.GM1983@kadam>
Hi Dan,
On Fri, Jun 25, 2021 at 1:02 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> On Fri, Jun 25, 2021 at 09:17:26AM -0700, bluez.test.bot@gmail.com wrote:
> > ##############################
> > Test: CheckPatch - FAIL - 0.59 seconds
> > Run checkpatch.pl script with rule in .checkpatch.conf
> > Bluetooth: sco: prevent information leak in sco_conn_defer_accept()
> > WARNING: Unknown commit id '2f69a82acf6f', maybe rebased or not pulled?
>
> I double checked the commit and it's correct. It's from 2013 so it's
> not clear how the bot got confused.
Yep, Ive seen this before with my own patches, perhaps there is
something with the CI tree which prevents checkpatch to locate the
commit id or something like that, @An, Tedd please have a look at CI
environment what could be causing this problem.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2021-06-25 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 15:00 [PATCH] Bluetooth: sco: prevent information leak in sco_conn_defer_accept() Dan Carpenter
2021-06-25 16:17 ` bluez.test.bot
2021-06-25 19:59 ` Dan Carpenter
2021-06-25 20:33 ` Luiz Augusto von Dentz [this message]
2021-07-08 7:11 ` bluez.test.bot
2021-07-22 14:14 ` [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=CABBYNZJoP5_d-K1hUt+G3N3KhgXoaokFRu_FQrrbYKctAqFhrg@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tedd.an@intel.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).