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]
Date:	Tue, 9 Jun 2015 13:38:53 +0000
From:	"Simmons, James A." <simmonsja@...l.gov>
To:	'Sudip Mukherjee' <sudipm.mukherjee@...il.com>,
	Dan Carpenter <dan.carpenter@...cle.com>
CC:	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Drokin <oleg.drokin@...el.com>,
	"lustre-devel@...ts.lustre.org" <lustre-devel@...ts.lustre.org>
Subject: RE: [lustre-devel] [PATCH v4 1/7] staging:lustre: move tcpip
	abstraction

>On Thu, Jun 04, 2015 at 10:34:20AM +0300, Dan Carpenter wrote:
>> On Thu, Jun 04, 2015 at 11:05:54AM +0530, Sudip Mukherjee wrote:
>> > On Wed, Jun 03, 2015 at 03:57:07PM -0400, James Simmons wrote:
>> > > Rename libcfs/linux/linux-tcpip.c to lnet/lnet/lib-socket.c
>> > looks like you have not just renamed the file, but there was also a change
>> > in the #include which is not mentioned in the commit message.
>> > 
>> 
>> That's obviously going to be part of moving the file.
>yes. path changed for libcfs.h. so that was updated.
>but there was also a new line
>#include "../../include/linux/lnet/lib-lnet.h"
>
>should that be part of moving the file also?

That is handle the move of some of the LNet function declarations in libcfs.h
to lib-lnet.h. That happens in patch number 4 of this series. I was trying to
minimize the diff between the tip of the Lustre development branch and
the upstream client.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists