From: "J. Bruce Fields" <bfields@fieldses.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
NeilBrown <neilb@suse.com>
Subject: Re: [PATCH] vfs: remove unnecessary fl_owner_t typedef
Date: Mon, 19 Mar 2018 10:27:13 -0400 [thread overview]
Message-ID: <20180319142713.GA24699@fieldses.org> (raw)
In-Reply-To: <20180317191415.GQ30522@ZenIV.linux.org.uk>
On Sat, Mar 17, 2018 at 07:14:15PM +0000, Al Viro wrote:
> On Sat, Mar 17, 2018 at 02:48:40PM -0400, J. Bruce Fields wrote:
> > This is a pretty simple patch that touches a lot of files. What's the
> > procedure for handling patches like this? I haven't had to do this
> > before.
>
> I'm not sure it's a good idea. We want it opaque - if anything, I would
> prefer to have anything mistakenly passing it to a function that takes
> a pointer scream like hell at build time. The current variant doesn't
> have such protection, but it can at least be grepped for. void * can't.
OK; dropping for now.
--b.
next prev parent reply other threads:[~2018-03-19 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 18:48 [PATCH] vfs: remove unnecessary fl_owner_t typedef J. Bruce Fields
2018-03-17 19:12 ` Jeff Layton
2018-03-17 19:14 ` Al Viro
2018-03-19 14:27 ` J. Bruce Fields [this message]
2018-03-18 20:39 ` NeilBrown
2018-03-19 14:27 ` J. Bruce Fields
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=20180319142713.GA24699@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=viro@ZenIV.linux.org.uk \
/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).