netdev - Re: linux-next: manual merge of the net-next tree with the vfs tree

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Mar 2015 23:24:26 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	netdev@...r.kernel.org, viro@...IV.linux.org.uk,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	hch@....de, ying.xue@...driver.com
Subject: Re: linux-next: manual merge of the net-next tree with the vfs tree

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Fri, 13 Mar 2015 13:15:43 +1100

> Today's linux-next merge of the net-next tree got a conflict in
> net/socket.c between commits 005139a14660 ("fs: remove ki_nbytes") and
> e9eab93cc2dc ("fs: don't allow to complete sync iocbs through
> aio_complete") from the vfs tree and commit 1b784140474e ("net: Remove
> iocb argument from sendmsg and recvmsg") from the net-next tree.
> 
> I fixed it up (mainly using the net-next version - see below) and can
> carry the fix as necessary (no action is required).

Al, how do you want to resolve this?
--
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