linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2] uhid: Remove local copy of uhid header
Date: Mon, 22 Nov 2021 15:46:44 -0800	[thread overview]
Message-ID: <CABBYNZJgpB8Y9gc92BupiBBkjyPf5SNkOBpp6B1qtYktxmAb_g@mail.gmail.com> (raw)
In-Reply-To: <45caaa82b56528fed03e534103f55f2ebbdc3885.camel@hadess.net>

Hi Bastien,

On Mon, Nov 22, 2021 at 3:06 PM Bastien Nocera <hadess@hadess.net> wrote:
>
> On Mon, 2021-11-22 at 13:17 -0800, Luiz Augusto von Dentz wrote:
> > From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >
> > uhid.h is part of kernel uapi nowadays so it can be included
> > directly from linux/uhid.h so this removes the local copy to use it
> > instead.
>
> This will cause the same problems that importing those headers into the
> repository was supposed to solve. If you remove those headers, then
> older distributions will be stuck on old kernel headers, and bluez
> compilations will regularly fail when it uses new structs, struct
> members, functions, or constants that are in the upstream uapi headers
> but not yet propagated to the user's distribution.

I'm not following you on this, the distros don't have uapi headers
that match their kernel release? Afaik being a kernel uapi means these
APIs are considered stable and I suspect they haven't been changed in
a while, you are right that this introduces a kernel dependency if we
were to use new members but I still think this is better than having
copies that at some point goes out of sync, specially when nothing
indicates that things like input_event was not accepted by the kernel.

> Strong NAK on this one and the uinput header change too.

I didn't introduce the usage of any new symbols, so the only new
requirement is that linux/uinput.h and linux/uhid.h headers exist, I
could however rollback if we have another way to check if those
headers exists use then otherwise we can keep using copies, perhaps
move then under linux/ directory, anyway it is not like we don't have
kernel dependencies already and we actually have been debating on
having the bluetooth socket definitions as part of the uapi instead of
libbluetooth, so we will need to sort out how we can update the
userspace parts with new kernel interface without breaking the build
on systems that don't actually ship with e.g. linux/bluetooth.h.

-- 
Luiz Augusto von Dentz

  reply	other threads:[~2021-11-22 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 21:17 [PATCH v2] uhid: Remove local copy of uhid header Luiz Augusto von Dentz
2021-11-22 21:33 ` [v2] " bluez.test.bot
2021-11-22 23:06 ` [PATCH v2] " Bastien Nocera
2021-11-22 23:46   ` Luiz Augusto von Dentz [this message]
2021-11-23  8:48     ` Bastien Nocera
2021-11-23 13:24       ` Marcel Holtmann
2021-11-23 21:30         ` Luiz Augusto von Dentz

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=CABBYNZJgpB8Y9gc92BupiBBkjyPf5SNkOBpp6B1qtYktxmAb_g@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.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 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).