Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754574AbdH1IYk (ORCPT ); Mon, 28 Aug 2017 04:24:40 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:35492 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751172AbdH1IYV (ORCPT ); Mon, 28 Aug 2017 04:24:21 -0400 Date: Mon, 28 Aug 2017 10:24:26 +0200 From: Greg KH To: Arvind Yadav Cc: oleg.drokin@intel.com, andreas.dilger@intel.com, jsimmons@infradead.org, john.hammond@intel.com, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org Subject: Re: [PATCH] staging: lustre: constify cl_lock_operations Message-ID: <20170828082426.GA1401@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 509 Lines: 12 On Sun, Aug 27, 2017 at 11:35:27AM +0530, Arvind Yadav wrote: > cl_lock_operations are not supposed to change at runtime. > cl_lock_slice_add is working with const cl_lock_operations. > So mark the non-const cl_lock_operations structs as const. > > Signed-off-by: Arvind Yadav > --- > drivers/staging/lustre/lustre/obdecho/echo_client.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Someone else already sent this same patch in, and it's already applied in my tree :(