All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the bluetooth tree
Date: Fri, 22 Nov 2019 11:07:11 +1100	[thread overview]
Message-ID: <20191122110711.3e894cc6@canb.auug.org.au> (raw)

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

Hi all,

After merging the bluetooth tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

net/bluetooth/hci_core.c: In function 'hci_dev_do_open':
net/bluetooth/hci_core.c:1447:8: warning: 'invalid_bdaddr' may be used uninitialized in this function [-Wmaybe-uninitialized]
 1447 |   bool invalid_bdaddr;
      |        ^~~~~~~~~~~~~~

Introduced by commit

  cadbc2f459be ("Bluetooth: Move error check into the right if-clause")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-11-22  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  0:07 Stephen Rothwell [this message]
     [not found] <PH0PR11MB51264FB7874380983C3A653BD3CF9@PH0PR11MB5126.namprd11.prod.outlook.com>
2022-05-16 18:18 ` linux-next: build warning after merge of the bluetooth tree Yury Norov
  -- strict thread matches above, loose matches on Subject: below --
2022-05-16  7:57 Stephen Rothwell
2022-05-23 22:22 ` Stephen Rothwell
2022-06-05 22:06   ` Stephen Rothwell
2022-06-05 22:40     ` Yury Norov
2022-06-06  1:16       ` Stephen Rothwell
2019-03-17 23:30 Stephen Rothwell
2017-11-14  0:56 Stephen Rothwell
2017-11-14  9:00 ` Hans de Goede

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=20191122110711.3e894cc6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marcel@holtmann.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 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.