From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id CF6797DF4 for ; Fri, 5 Dec 2014 19:42:27 +0100 (CET) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1Xwxpd-0004xA-HO; Fri, 05 Dec 2014 13:42:23 -0500 Date: Fri, 5 Dec 2014 13:42:15 -0500 From: Neil Horman To: Thomas Monjalon Message-ID: <20141205184215.GE29245@hmsreliant.think-freely.org> References: <1417729325-9410-1-git-send-email-linville@tuxdriver.com> <128892442.7P4I1l0Tzy@xps13> <5011667.KPTrBnDxk4@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5011667.KPTrBnDxk4@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Accessing Virtual Function Device on Guest Machine using VFIO X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 18:42:28 -0000 On Fri, Dec 05, 2014 at 07:08:55PM +0100, Thomas Monjalon wrote: > Hi, > > Please don't reply to a previous email to start a different topic. > You can check how it looks here: > http://thread.gmane.org/gmane.comp.networking.dpdk.devel > > > "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." > > Please remove this disclaimer. > It's not specifically against you but it's at least the tenth time I say this > to an Aricent guy. This disclaimer should force us to remove your message > (even in the archives). So we should maybe block all the emails from aricent.com. > +1. These disclaimers are not only most likely toothless (though IANAL), but it does place the community in the position of either needing to take the effort to scrub your emails from the archives to be in compliance with the disclamer, or to take the legal risk that such a disclaimer actually has merit. If your company can't abide by you removing such a notice, than that company can't participate in open source. Neil > -- > Thomas >