From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Jeff Layton <jlayton@kernel.org>,
Kees Cook <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>,
Dave Chinner <david@fromorbit.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net,
linux-afs@lists.infradead.org, ceph-devel@vger.kernel.org,
CIFS <linux-cifs@vger.kernel.org>,
samba-technical@lists.samba.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-hardening@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context
Date: Thu, 9 Jun 2022 15:05:46 -0700 [thread overview]
Message-ID: <CAHk-=whGrrF20LshkNGJ41UmNN13MU6x0_npwaJQi9cr626GQQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgkwKyNmNdKpQkqZ6DnmUL-x9hp0YBnUGjaPFEAdxDTbw@mail.gmail.com>
On Thu, Jun 9, 2022 at 3:04 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> IOW, I think you really should do something like the attached on top
> of this all.
Just to clarify: I did apply your patch. It's an improvement on what
used to go on.
I just think it wasn't as much of an improvement that it should have
been, and that largely untested patch I attached is I think another
step in a better direction.
Linus
next prev parent reply other threads:[~2022-06-09 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 20:46 [PATCH] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context David Howells
2022-06-09 22:04 ` Linus Torvalds
2022-06-09 22:05 ` Linus Torvalds [this message]
2022-06-10 18:06 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2022-05-19 13:44 David Howells
2022-05-19 14:05 ` Kees Cook
2022-05-19 15:33 ` Jeff Layton
2022-05-23 1:01 ` Xiubo Li
2022-05-24 0:29 ` Xiubo Li
2022-05-27 12:27 ` David Howells
2022-05-27 20:45 ` Kees Cook
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='CAHk-=whGrrF20LshkNGJ41UmNN13MU6x0_npwaJQi9cr626GQQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=ceph-devel@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--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-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).