From: Al Viro <viro@ZenIV.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Vivek Goyal <vgoyal@redhat.com>,
linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v4 7/9] vfs: export alloc_inode() and destroy_inode()
Date: Fri, 18 May 2018 16:02:19 +0100 [thread overview]
Message-ID: <20180518150219.GR30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1526632177-28832-8-git-send-email-amir73il@gmail.com>
On Fri, May 18, 2018 at 11:29:35AM +0300, Amir Goldstein wrote:
> They are needed by overlayfs.
NAK, and kindly abstain from patently false declarative statements
in commit messages.
next prev parent reply other threads:[~2018-05-18 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 8:29 [PATCH v4 0/9] Overlayfs create object related fixes Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 1/9] ovl: remove WARN_ON() real inode attributes mismatch Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 2/9] ovl: strip debug argument from ovl_do_ helpers Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 3/9] ovl: struct cattr cleanups Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 4/9] ovl: create helper ovl_create_temp() Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 5/9] ovl: make ovl_create_real() cope with vfs_mkdir() safely Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 6/9] vfs: factor out iget5_prealloc() Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 7/9] vfs: export alloc_inode() and destroy_inode() Amir Goldstein
2018-05-18 15:02 ` Al Viro [this message]
2018-05-18 8:29 ` [PATCH v4 8/9] ovl: Pass argument to ovl_get_inode() in a structure Amir Goldstein
2018-05-18 8:29 ` [PATCH v4 9/9] ovl: use iget5_prealloc() to hash a newly created inode Amir Goldstein
2018-05-18 10:14 ` Miklos Szeredi
2018-05-18 14:08 ` Amir Goldstein
2018-05-18 14:24 ` Miklos Szeredi
2018-05-18 15:03 ` Al Viro
2018-05-18 15:11 ` Miklos Szeredi
2018-05-18 15:14 ` Miklos Szeredi
2018-05-18 15:36 ` Amir Goldstein
2018-05-18 15:57 ` Miklos Szeredi
2018-05-18 16:53 ` Amir Goldstein
2018-05-18 15:40 ` Al Viro
2018-05-18 16:01 ` Miklos Szeredi
2018-05-22 15:21 ` Miklos Szeredi
2018-05-23 8:11 ` Amir Goldstein
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=20180518150219.GR30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@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.