From: Al Viro <viro@zeniv.linux.org.uk>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
axboe@kernel.dk
Subject: Re: [PATCH REPOST] docs: Add struct file refcounting and SCM_RIGHTS mess info
Date: Thu, 11 Apr 2019 22:30:13 +0100 [thread overview]
Message-ID: <20190411213013.GI2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190411142308.179247a4@lwn.net>
On Thu, Apr 11, 2019 at 02:23:08PM -0600, Jonathan Corbet wrote:
> docs: Add struct file refcounting and SCM_RIGHTS mess info
>
> Work up some text posted by Al and add it to the filesystem manual.
>
> Co-developed-by: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> ---
> This is the third sending of this patch. Al, you *did* ask me to run it
> past you before putting it in; do you think you might get a chance to have
> a look sometime soon?
Will do, hopefully tonight...
next prev parent reply other threads:[~2019-04-11 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 20:23 [PATCH REPOST] docs: Add struct file refcounting and SCM_RIGHTS mess info Jonathan Corbet
2019-04-11 21:30 ` Al Viro [this message]
2019-04-12 21:53 ` Al Viro
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=20190411213013.GI2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.