From: Jeff Layton <jlayton@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: keescook@chromium.org, Jonathan Corbet <corbet@lwn.net>,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Marc Dionne <marc.dionne@auristor.com>,
Xiubo Li <xiubli@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
Steve French <smfrench@gmail.com>,
William Kucharski <william.kucharski@oracle.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-doc@vger.kernel.org, v9fs-developer@lists.sourceforge.net,
linux-afs@lists.infradead.org, ceph-devel@vger.kernel.org,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-fsdevel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context
Date: Mon, 23 May 2022 07:05:31 -0400 [thread overview]
Message-ID: <e4fcdf88a9b35a9f1ca6e75fdf75ad469f824380.camel@kernel.org> (raw)
In-Reply-To: <658391.1653302817@warthog.procyon.org.uk>
On Mon, 2022-05-23 at 11:46 +0100, David Howells wrote:
> Jeff Layton <jlayton@kernel.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@kernel.org>
next prev parent reply other threads:[~2022-05-23 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:47 [PATCH v2] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context David Howells
2022-05-23 10:36 ` Jeff Layton
2022-05-23 10:46 ` David Howells
2022-05-23 11:05 ` Jeff Layton [this message]
2022-05-24 9:50 ` Xiubo Li
2022-05-24 9:51 ` Xiubo Li
2022-05-24 10:12 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4fcdf88a9b35a9f1ca6e75fdf75ad469f824380.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ceph-devel@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=ericvh@gmail.com \
--cc=idryomov@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=marc.dionne@auristor.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
--cc=xiubli@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).