From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: [PATCH 0/4] module: add support for unsafe, tainting parameters Date: Thu, 21 Aug 2014 10:00:48 +0300 Message-ID: <87oavemin3.fsf@intel.com> References: <87wqac87dq.fsf@rustcorp.com.au> <87ppfvi1hx.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id F103489D9A for ; Thu, 21 Aug 2014 00:01:03 -0700 (PDT) In-Reply-To: <87ppfvi1hx.fsf@rustcorp.com.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Rusty Russell , Daniel Vetter Cc: Li Zhong , intel-gfx , Linux Kernel Mailing List , Jean Delvare , Andrew Morton , Jon Mason List-Id: intel-gfx@lists.freedesktop.org On Wed, 20 Aug 2014, Rusty Russell wrote: > I've applied this cleanup on top, however. > > Cheers, > Rusty. > > Subject: param: check for tainting before calling set op. > > This means every set op doesn't need to call it, and it can move into > params.c. Much better, thanks. I was looking for a way to do something like this, but obviously didn't look hard enough. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center