From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 1/8] cifs: Fix xattr name checks Date: Thu, 14 Apr 2016 05:59:20 +0100 Message-ID: <20160414045920.GT25498@ZenIV.linux.org.uk> References: <20160413182026.GR25498@ZenIV.linux.org.uk> <1460586620-5717-1-git-send-email-agruenba@redhat.com> <1460586620-5717-2-git-send-email-agruenba@redhat.com> <20160414043718.GS25498@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andreas Gruenbacher , Steve French , "linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cluster-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org To: Steve French Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Wed, Apr 13, 2016 at 11:43:19PM -0500, Steve French wrote: > If you are planning to merge it in next few weeks (they fix bugs, and > are safe so why not), I can simply just back out my changes from > cifs-2.6.git for-next branch and let you merge the trivial checkpatch > cleanup attached. Do you want it in mainline before 4.6-final? If that can wait until 4.7-rc1 (and these are both old and not earth-shattering), I've no problem with putting the entire series (including cleanup) into a branch merged into vfs.git#for-next; if you consider it 4.6-final fodder, it's probably better be your pull request. PS: are there any docs re setup for cifs testing? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Date: Thu, 14 Apr 2016 05:59:20 +0100 Subject: [Cluster-devel] [PATCH 1/8] cifs: Fix xattr name checks In-Reply-To: References: <20160413182026.GR25498@ZenIV.linux.org.uk> <1460586620-5717-1-git-send-email-agruenba@redhat.com> <1460586620-5717-2-git-send-email-agruenba@redhat.com> <20160414043718.GS25498@ZenIV.linux.org.uk> Message-ID: <20160414045920.GT25498@ZenIV.linux.org.uk> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Apr 13, 2016 at 11:43:19PM -0500, Steve French wrote: > If you are planning to merge it in next few weeks (they fix bugs, and > are safe so why not), I can simply just back out my changes from > cifs-2.6.git for-next branch and let you merge the trivial checkpatch > cleanup attached. Do you want it in mainline before 4.6-final? If that can wait until 4.7-rc1 (and these are both old and not earth-shattering), I've no problem with putting the entire series (including cleanup) into a branch merged into vfs.git#for-next; if you consider it 4.6-final fodder, it's probably better be your pull request. PS: are there any docs re setup for cifs testing?