From: David Howells <dhowells@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: dhowells@redhat.com, jlayton@kernel.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-fsdevek@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context
Date: Fri, 27 May 2022 13:27:33 +0100 [thread overview]
Message-ID: <3598052.1653654453@warthog.procyon.org.uk> (raw)
In-Reply-To: <202205190704.1DC660E5E@keescook>
Hi Kees,
Is v2 good for you? I realise I left your R-b attached to it when I posted
it, but I can remove that if you don't have time to review it.
David
next prev parent reply other threads:[~2022-05-27 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 13:44 [PATCH] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context David Howells
2022-05-19 14:05 ` Kees Cook
2022-05-27 12:27 ` David Howells [this message]
2022-05-27 20:45 ` Kees Cook
2022-05-19 15:33 ` Jeff Layton
2022-05-20 9:15 ` kernel test robot
2022-05-23 1:01 ` Xiubo Li
2022-05-24 0:29 ` Xiubo Li
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 20:46 David Howells
2022-06-09 22:04 ` Linus Torvalds
2022-06-09 22:05 ` Linus Torvalds
2022-06-10 18:06 ` David Howells
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=3598052.1653654453@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=ceph-devel@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=ericvh@gmail.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.