linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: Re: linux-next: build warning after merge of the bluetooth tree
Date: Tue, 14 Nov 2017 10:00:26 +0100	[thread overview]
Message-ID: <d6d5041b-5cec-0205-62cb-fa468d41a6ea@redhat.com> (raw)
In-Reply-To: <20171114115633.1f4db312@canb.auug.org.au>

Hi,

On 14-11-17 01:56, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the bluetooth tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/bluetooth/Kconfig:35:warning: multi-line strings not supported
> 
> Introduced by commit
> 
>    86be3c232877 ("Bluetooth: btusb: Add a Kconfig option to enable USB autosuspend by default")
> 
> There is a missing close double quote ...

Ugh, sorry about that, a patch (on top of the original) fixing this
is coming up right away.

Regards,

Hans

  reply	other threads:[~2017-11-14  9:00 UTC|newest]

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

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=d6d5041b-5cec-0205-62cb-fa468d41a6ea@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=sfr@canb.auug.org.au \
    /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).