[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241217065129.10677f69@kernel.org>
Date: Tue, 17 Dec 2024 06:51:29 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Li Li <dualli@...gle.com>
Cc: Carlos Llamas <cmllamas@...gle.com>, corbet@....net,
davem@...emloft.net, Eric Dumazet <edumazet@...gle.com>, pabeni@...hat.com,
donald.hunter@...il.com, Greg KH <gregkh@...uxfoundation.org>, Arve
Hjønnevåg <arve@...roid.com>, tkjos@...roid.com,
maco@...roid.com, "Joel Fernandes (Google)" <joel@...lfernandes.org>,
brauner@...nel.org, Suren Baghdasaryan <surenb@...gle.com>, arnd@...db.de,
masahiroy@...nel.org, bagasdotme@...il.com, horms@...nel.org, LKML
<linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
netdev@...r.kernel.org, Hridya Valsaraju <hridya@...gle.com>, Steven
Moreland <smoreland@...gle.com>, Android Kernel Team
<kernel-team@...roid.com>
Subject: Re: [PATCH net-next v10 2/2] binder: report txn errors via generic
netlink
On Mon, 16 Dec 2024 19:53:40 -0800 Li Li wrote:
> > > These are automatically generated from the yaml file. So let's just
> > > keep them as is.
> > > But it's a good suggestion to the owner of yaml parser.
> >
> > I think the unusual naming comes from fact that you call your netlink
> > family binder_netlink. It's sort of like adding the word sysfs to the
> > name of a sysfs file. I mean the user visible name, not code
> > references...
> >
> > s/binder_netlink/binder/ will clean this up..
>
> I did consider that but unfortunately that would result in a
> conflicting binder.h in uapi header.
What exactly is conflicting? The name of the header itself?
You can set the uapi header name using the uapi-header property.
Powered by blists - more mailing lists