From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f193.google.com ([209.85.210.193]:34603 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726325AbeJRUNh (ORCPT ); Thu, 18 Oct 2018 16:13:37 -0400 Received: by mail-pf1-f193.google.com with SMTP id f78-v6so9042339pfe.1 for ; Thu, 18 Oct 2018 05:12:53 -0700 (PDT) Date: Thu, 18 Oct 2018 23:12:46 +1100 From: Matthew Bobrowski To: Amir Goldstein Cc: Jan Kara , linux-api@vger.kernel.org, Steve Grubb , linux-fsdevel Subject: Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM Message-ID: <20181018121245.GC3620@workstation> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 18, 2018 at 01:07:37PM +0300, Amir Goldstein wrote: > On Wed, Oct 17, 2018 at 12:04 PM Matthew Bobrowski > wrote: > > > > Please note that all modifications here are based on the changes Amir has > > made around deprecating some of the previously exposed UAPI constants. The > > branch which my changes are based on can be found here: > > > > https://github.com/amir73il/linux/tree/fanotify_api-v3 > > > > Please note that this branch is slightly outdated. > When testing you should rebase your patches on top of > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify Perfect, and will do. Thanks for sending that through. > I don't think that you need to re-post unless Jan wants a re-post of patch #3 > because there shouldn't be any rebase conflicts. Yeah, that's what I mentioned within my previous email. I mean, the ammendments to these files are minimal, so I don't really know whether I need to submit a completely new patch series through for each update after a review? Happy to re-post, if required. -- Matthew Bobrowski