[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e4fcdf88a9b35a9f1ca6e75fdf75ad469f824380.camel@kernel.org>
Date: Mon, 23 May 2022 07:05:31 -0400
From: Jeff Layton <jlayton@...nel.org>
To: David Howells <dhowells@...hat.com>
Cc: keescook@...omium.org, Jonathan Corbet <corbet@....net>,
Eric Van Hensbergen <ericvh@...il.com>,
Latchesar Ionkov <lucho@...kov.net>,
Dominique Martinet <asmadeus@...ewreck.org>,
Christian Schoenebeck <linux_oss@...debyte.com>,
Marc Dionne <marc.dionne@...istor.com>,
Xiubo Li <xiubli@...hat.com>,
Ilya Dryomov <idryomov@...il.com>,
Steve French <smfrench@...il.com>,
William Kucharski <william.kucharski@...cle.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
linux-doc@...r.kernel.org, v9fs-developer@...ts.sourceforge.net,
linux-afs@...ts.infradead.org, ceph-devel@...r.kernel.org,
linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
linux-fsdevel@...r.kernel.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] netfs: Fix gcc-12 warning by embedding vfs inode in
netfs_i_context
On Mon, 2022-05-23 at 11:46 +0100, David Howells wrote:
> Jeff Layton <jlayton@...nel.org> wrote:
>
> >
> > Note that there are some conflicts between this patch and some of the
> > patches in the current ceph-client/testing branch. Depending on the
> > order of merge, one or the other will need to be fixed.
>
> Do you think it could be taken through the ceph tree?
>
> David
>
Since this touches a lot of non-ceph code, it may be best to just plan
to merge it ASAP, and we'll just base our merge branch on top of it.
Ilya/Xiubo, do you have an opinion here?
--
Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists