netdev - Re: [net-next:master 647/682] fib_semantics.c:undefined reference to `_

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20151005.234226.1882984429611604223.davem@davemloft.net>
Date:	Mon, 05 Oct 2015 23:42:26 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	pch@...bogen.com
Cc:	fengguang.wu@...el.com, kbuild-all@...org, netdev@...r.kernel.org
Subject: Re: [net-next:master 647/682] fib_semantics.c:undefined reference
 to `__divdi3'

From: Peter Nørlund <pch@...bogen.com>
Date: Mon, 5 Oct 2015 23:31:58 +0200

> What is the proper way to supply fixes for this kind of errors? Should
> I submit the original patches again with the bug fixed, or should I
> submit a patch fixing this particular problem? I imagine bisecting
> becomes annoying when a particular commit doesn't compile.

Once a patch is in my tree, it is part of the permanent record and
cannot be removed.  Therefore you must send me a fix for this
problem.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html