From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5786F1EB51 for ; Wed, 17 Jan 2024 13:26:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705497972; cv=none; b=U8wFu+PMMDl8A3ivL51IJg2VkBYAJnbbXGN2tNpNFkobr/NJQMVdZ9jI18K8nmpQXOs5yZgFi7d5yH7wBQot962xnw5772APFg0bTW+40ap4Kdso28WaD4XMe/plyAVSJB9hsbF99UOpR3FV41SqZcmxAHSvSnqPTXdPqCbcIoA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705497972; c=relaxed/simple; bh=OPOoP9UgIckMad4MC0xQT4ogrYoDI41gySdqC4ReyPA=; h=DKIM-Signature:Received:X-MC-Unique:Received:Received: Organization:From:In-Reply-To:References:To:cc:Subject: MIME-Version:Content-Type:Content-ID:Date:Message-ID:X-Scanned-By; b=IRQhrlvjll8IeJjFS9WcSSB+3P0X9Fq/oMjbqHPTcIP4CUW4lFNV+09xpz174cw+sz/qfzj8tN8iDfmdauhmvNg+SMo4m3eJFUlTTJAPOthFOv8sca/Xq+FWxi1dubaCJYfH9F28VIm9wUtHrKLP6D980AF6ItQ/aGzabtU1KtU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=GgKePF9Q; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="GgKePF9Q" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1705497970; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FsSzWO6NIq2VcxMsblj4BWBZVF2ZpmLB+3az7ONnZQM=; b=GgKePF9QlpvrxiyCN+DVRC5N2CPIkK8gwD+XpsxSs/snfTZiCvmFqlaxIma3w1DXrKGwo3 WA6+eWh11DWqJPNuUQvtttnmN2q/JzpbKHQ5RbNWjR30UCcai+nlkyz+uzEgcRGvd0+OKH PXen3MyhboRQbq8bz6xe4sUNc8Novc4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-328-Oe-laUu7NUWY9jmEaxHoOQ-1; Wed, 17 Jan 2024 08:26:06 -0500 X-MC-Unique: Oe-laUu7NUWY9jmEaxHoOQ-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 63A7B867943; Wed, 17 Jan 2024 13:26:02 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.67]) by smtp.corp.redhat.com (Postfix) with ESMTP id 63FC3492BC6; Wed, 17 Jan 2024 13:25:55 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20240116-flsplit-v1-2-c9d0f4370a5d@kernel.org> References: <20240116-flsplit-v1-2-c9d0f4370a5d@kernel.org> <20240116-flsplit-v1-0-c9d0f4370a5d@kernel.org> To: Jeff Layton cc: Christian Brauner , Alexander Viro , Eric Van Hensbergen , Latchesar Ionkov , Dominique Martinet , Christian Schoenebeck , David Howells , Marc Dionne , Xiubo Li , Ilya Dryomov , Alexander Aring , David Teigland , Miklos Szeredi , Andreas Gruenbacher , Trond Myklebust , Anna Schumaker , Chuck Lever , Neil Brown , Olga Kornievskaia , Dai Ngo , Tom Talpey , Jan Kara , Mark Fasheh , Joel Becker , Joseph Qi , Steve French , Paulo Alcantara , Ronnie Sahlberg , Shyam Prasad N , Namjae Jeon , Sergey Senozhatsky , Steven Rostedt , Masami Hiramatsu , Mathieu Desnoyers , linux-kernel@vger.kernel.org, v9fs@lists.linux.dev, linux-afs@lists.infradead.org, ceph-devel@vger.kernel.org, gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, ocfs2-devel@lists.linux.dev, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, linux-trace-kernel@vger.kernel.org Subject: Re: [PATCH 02/20] filelock: add coccinelle scripts to move fields to struct file_lock_core Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2782046.1705497954.1@warthog.procyon.org.uk> Date: Wed, 17 Jan 2024 13:25:54 +0000 Message-ID: <2782047.1705497954@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 Do we need to keep these coccinelle scripts for posterity? Or can they just be included in the patch description of the patch that generates them? David