All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	backports@vger.kernel.org
Subject: Re: [PATCH v2] backports: add ktime_get_seconds()
Date: Tue, 08 Dec 2015 10:04:04 +0100	[thread overview]
Message-ID: <1449565444.4154.1.camel@sipsolutions.net> (raw)
In-Reply-To: <56669864.3050404@broadcom.com> (sfid-20151208_094430_942811_4B1A5954)

On Tue, 2015-12-08 at 09:44 +0100, Arend van Spriel wrote:
> 
> I hit a duplicate export of this function against Fedora 22 kernel 
> (v4.0.4). So they apparently backported it in their kernel. So I 
> manually removed the function from backports tarball. Could this be 
> automated by looking at Module.symvers of the kernel we build
> against? I will explore that if you guys consider it useful.
> 

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? :)

I once considered something similar but by actually test-compiling
something against the kernel - that worked (even for backported
inlines) but was awfully slow ...

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

  reply	other threads:[~2015-12-08  9:04 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 [this message]
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
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=1449565444.4154.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    /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.