All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>,
	Arend van Spriel <arend@broadcom.com>,
	backports@vger.kernel.org
Subject: Re: [PATCH v2] backports: add ktime_get_seconds()
Date: Wed, 9 Dec 2015 23:52:28 +0100	[thread overview]
Message-ID: <5668B0AC.2080602@hauke-m.de> (raw)
In-Reply-To: <1449567481.4154.9.camel@sipsolutions.net>

On 12/08/2015 10:38 AM, Johannes Berg wrote:
> On Tue, 2015-12-08 at 10:28 +0100, Arend van Spriel wrote:
>>  
>> Basically the list would be the exported symbols from the backports 
>> module, ie. compat.ko, right?
>>
> 
> Perhaps, I think it's slightly more complicated.
> 
> For one, we mostly prefix them with backport_, so just using as-is
> won't work.
> 
> Secondly, we might sometimes intentionally do that, even though the
> original function *does* exist, like with debugfs_create_bool() that
> changed function signature.
> 
> I think it'd be safer to just do it one by one - but we might be able
> to get rid of a lot of the RHEL/ubuntu/whatever ifdefs that way?
> 
> We might also be able to use them to ifdef some inlines that belong to
> it? Overall it seems better to just do it by hand but as a better
> mechanism than checking kernel versions?
> 
> johannes

We could search backport/compat/*.c for EXPORT_SYMBOL() and create the
list based on that. Using compat.ko for that would mean we have to
compile first.
Based on this data we can check if the kernel would export this function
and create a "#define HAVE_FUNFION_NAME 1"

Hauke

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2015-12-09 22:52 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
2015-12-08  9:38           ` Johannes Berg
2015-12-09 22:52             ` Hauke Mehrtens [this message]
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=5668B0AC.2080602@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --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.