Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 30 Apr 2019 17:04:56 +0200
From:   Stephan Gerhold <stephan@gerhold.net>
To:     Marcel Holtmann <marcel@holtmann.org>,
        Johan Hedberg <johan.hedberg@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: btbcm: Add default address for BCM2076B1
Message-ID: <20190430150456.GA50466@gerhold.net>
References: <20190305130901.56660-1-stephan@gerhold.net>
 <20190305130901.56660-2-stephan@gerhold.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190305130901.56660-2-stephan@gerhold.net>
User-Agent: Mutt/1.11.4 (2019-03-13)
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Marcel, Hi Johan,

On Tue, Mar 05, 2019 at 02:09:01PM +0100, Stephan Gerhold wrote:
> BCM2076B1 appears to use 20:76:A0:00:56:79 as default address.
> This address is used by at least 5 devices with the AMPAK AP6476
> module and is also suspicious because it starts with the chip name
> 2076 (followed by a different revision A0 for some reason).
> 
> Add it to the list of default addresses and leave it up to the
> user to configure a valid one.
> 
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
>  drivers/bluetooth/btbcm.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 

As far as I can tell, you have applied the first patch of this series,
but forgot about this one. :)

It does not apply as-is anymore since you applied the patch from
Ferry Toth first, but it still applies cleanly with with 
"git am --3way".

Is that fine for you or should I re-send it on top of latest
bluetooth-next?

Thanks,
Stephan