[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1491596832.5800.21.camel@sipsolutions.net>
Date: Fri, 07 Apr 2017 22:27:12 +0200
From: Johannes Berg <johannes@...solutions.net>
To: David Miller <davem@...emloft.net>
Cc: pablo@...filter.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, jiri@...nulli.us
Subject: Re: [RFC 0/3] netlink: extended error reporting
On Fri, 2017-04-07 at 12:55 -0700, David Miller wrote:
>
> One idea. We use the macro thing to generate a "netlink.pot" file
> and then some userland tree can contain the latest netlink.pot and
> the translations.
Right. For the record - since we just talked about it - I was thinking
of putting it into a special section so that we could easily write a
script to generate the pot file from the kernel binary after doing
"allyesconfig" or collecting it from modules or so.
Thinking of modules though - do we need to adjust the module loading
code to load a new section? I'll have to look into that.
johannes
Powered by blists - more mailing lists