| 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
| ||
|
Message-ID: <20160519114548.3524ac02@canb.auug.org.au>
Date: Thu, 19 May 2016 11:45:48 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Doug Ledford <dledford@...hat.com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Matan Barak <matanb@...lanox.com>,
Amir Vadai <amirva@...lanox.com>,
"David S. Miller" <davem@...emloft.net>
Subject: linux-next: manual merge of the rdma tree with Linus' tree
Hi Doug,
Today's linux-next merge of the rdma tree got a conflict in:
include/linux/mlx5/driver.h
between commit:
43a335e055bb ("net/mlx5_core: Flow counters infrastructure")
from Linus' tree and commit:
94c6825e0ff7 ("net/mlx5_core: Use tasklet for user-space CQ completion events")
from the rdma tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/mlx5/driver.h
index 07b504f7eb84,5a41f9003941..000000000000
--- a/include/linux/mlx5/driver.h
+++ b/include/linux/mlx5/driver.h
@@@ -41,7 -41,7 +41,8 @@@
#include <linux/slab.h>
#include <linux/vmalloc.h>
#include <linux/radix-tree.h>
+#include <linux/workqueue.h>
+ #include <linux/interrupt.h>
#include <linux/mlx5/device.h>
#include <linux/mlx5/doorbell.h>
Powered by blists - more mailing lists