From: David Howells <dhowells@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: dhowells@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Dominique Martinet <asmadeus@codewreck.org>,
Marc Dionne <marc.dionne@auristor.com>,
Steve French <sfrench@samba.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
v9fs-developer@lists.sourceforge.net,
linux-afs@lists.infradead.org, CIFS <linux-cifs@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] fscache, 9p, afs, cifs, nfs: Deal with some warnings from W=1
Date: Mon, 20 Sep 2021 19:16:13 +0100 [thread overview]
Message-ID: <2976712.1632161773@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAH2r5murR7TbC9BtSgWyrJVC-YG5dUba2ekZTvX75gg4ukaAZw@mail.gmail.com>
Steve French <smfrench@gmail.com> wrote:
> For the cifs ones in connect.c (and also ioctl.c), I had submitted a
> patch in rc1 for these (haven't heard back on that) but did not submit
> kerneldoc fixup for fs/cifs/misc.c. They seem trivial and safe, do
> you want to split those out and I can put them in?
I can, though the reason I did the patch is that the warnings are always
popping up in what I'm doing. I can drop the patch from mine when I'm done, I
guess.
David
next prev parent reply other threads:[~2021-09-20 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:14 [RFC PATCH] fscache, 9p, afs, cifs, nfs: Deal with some warnings from W=1 David Howells
2021-09-20 12:37 ` Matthew Wilcox
2021-09-20 12:47 ` David Howells
2021-09-20 13:02 ` Dominique Martinet
2021-09-20 17:59 ` Steve French
2021-09-20 18:16 ` David Howells [this message]
2021-09-23 19:08 ` Fwd: " Steve French
2021-09-28 8:46 ` 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=2976712.1632161773@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=asmadeus@codewreck.org \
--cc=jlayton@kernel.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-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=mchehab@kernel.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=trond.myklebust@hammerspace.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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.