From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Hauke Mehrtens <hauke@hauke-m.de>, <backports@vger.kernel.org>
Subject: Re: [PATCH v2] backports: add ktime_get_seconds()
Date: Tue, 8 Dec 2015 10:28:40 +0100 [thread overview]
Message-ID: <5666A2C8.3070002@broadcom.com> (raw)
In-Reply-To: <1449566082.4154.6.camel@sipsolutions.net>
On 12/08/2015 10:14 AM, Johannes Berg wrote:
> On Tue, 2015-12-08 at 10:04 +0100, Johannes Berg wrote:
>>
>> That's not a bad idea. We could have a script that creates some kind
>> of
>> header file with #define HAVE_KTIME_GET_SECONDS and then we could use
>> that. We could even just do that for every single exported functions,
>> that will just be a few hundred lines but shouldn't matter much? :)
>>
>
> Ok maybe not - on a very small test configuration for me that's
> actually something like 6.5k lines...
>
> I guess then we could ship a list of functions we want to look at, like
> a file that simply lists one function per line:
Basically the list would be the exported symbols from the backports
module, ie. compat.ko, right?
Gr. AvS
> symbols-check:
>>>>
> ktime_get_seconds
> <<<
>
> and then we can do something like
>
> grep -f symbols-check /path/to/Module.symvers | \
> cut -f2 | \
> tr 'a-z' 'A-Z' | \
> sed 's/^/#define HAVE_/;s/$/ 1/' \
> > backport-include/backport/existing-symbols.h
>
> and include that in the right place?
>
> johannes
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-12-08 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 11:52 [PATCH v2] backports: add ktime_get_seconds() Johannes Berg
2015-10-28 21:17 ` Arend van Spriel
2015-10-31 22:03 ` Arend van Spriel
2015-11-01 7:47 ` Johannes Berg
2015-11-07 17:08 ` Hauke Mehrtens
2015-12-08 8:44 ` Arend van Spriel
2015-12-08 9:04 ` Johannes Berg
2015-12-08 9:14 ` Johannes Berg
2015-12-08 9:28 ` Arend van Spriel [this message]
2015-12-08 9:38 ` Johannes Berg
2015-12-09 22:52 ` Hauke Mehrtens
2015-12-09 22:56 ` Johannes Berg
2015-12-09 22:48 ` Hauke Mehrtens
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=5666A2C8.3070002@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=johannes@sipsolutions.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.