Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 20 Sep 2022 14:03:27 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     davem@davemloft.net, linux-bluetooth@vger.kernel.org,
        netdev@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: pull request: bluetooth 2022-09-09
Message-ID: <20220920140327.5eda455d@kernel.org>
In-Reply-To: <CABBYNZLhMRbvhhb-9Ho-qVarC+KLiFyxiaypHWW=NPqHXYTU0w@mail.gmail.com>
References: <20220909201642.3810565-1-luiz.dentz@gmail.com>
        <CABBYNZKHUbqYyevHRZ=6rLA0GAE20mLRHAj9JnFNuRn7VHrEeA@mail.gmail.com>
        <20220919180419.0caa435a@kernel.org>
        <CABBYNZLhMRbvhhb-9Ho-qVarC+KLiFyxiaypHWW=NPqHXYTU0w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 20 Sep 2022 13:56:45 -0700 Luiz Augusto von Dentz wrote:
> > > Looks like this still hasn't been applied, is there any problem that
> > > needs to be fixed?  
> >
> > Sorry about the delay, we were all traveling to Linux Plumbers.
> > Pulling now.
> >
> > Any reason why struct hci_dev_info is not under include/uapi ?  
> 
> None of Bluetooth APIs are there, at some point I was discussing with
> Marcel that we should probably fix that so we can properly expose
> headers to userspace as right now this depends on bluez library which
> is something we want to deprecate.

It'd be great if for no other reason just to make it very clear 
that the structures are uAPI during review.