From: Seth Forshee <seth.forshee@canonical.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: containers@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org,
Tyler Hicks <tyler.hicks@canonical.com>,
Christian Brauner <christian.brauner@canonical.com>
Subject: Re: shiftfs status and future development
Date: Fri, 15 Jun 2018 15:17:28 -0500 [thread overview]
Message-ID: <20180615201728.GL30028@ubuntu-xps13> (raw)
In-Reply-To: <1529080549.4048.14.camel@HansenPartnership.com>
On Fri, Jun 15, 2018 at 09:35:49AM -0700, James Bottomley wrote:
> On Fri, 2018-06-15 at 10:46 -0500, Seth Forshee wrote:
> [...]
> > Subject: [PATCH] shiftfs: Forward port to 4.17-rc6
> >
> > Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
> > ---
> > fs/shiftfs.c | 17 +++++++++--------
> > 1 file changed, 9 insertions(+), 8 deletions(-)
> >
> > diff --git a/fs/shiftfs.c b/fs/shiftfs.c
> > index ea8ac57b3ce1..fa0797bd7880 100644
> > --- a/fs/shiftfs.c
> > +++ b/fs/shiftfs.c
> > @@ -109,12 +109,12 @@ static void shiftfs_d_release(struct dentry
> > *dentry)
> >
> > static struct dentry *shiftfs_d_real(struct dentry *dentry,
> > const struct inode *inode,
> > - unsigned int flags)
> > + unsigned int open_flag
>
> Well, that's an oopsie: I already have this change in my code base. I
> think I probably did it at the last minute for a conference
> presentation (the log indicates it was done in the 4.14 timeframe) and
> then forgot to repost the patches, which would explain why it's still
> nicely compiling for me ...
>
> I can repost so we've got code to hang the discussion on.
That would be great, thanks!
Seth
prev parent reply other threads:[~2018-06-15 20:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:44 shiftfs status and future development Seth Forshee
2018-06-15 13:56 ` Serge E. Hallyn
2018-06-15 14:59 ` Seth Forshee
2018-06-15 15:25 ` Matthew Wilcox
2018-06-15 15:56 ` Aleksa Sarai
2018-06-15 16:09 ` James Bottomley
2018-06-15 17:04 ` Aleksa Sarai
2018-06-15 17:22 ` James Bottomley
2018-06-15 20:47 ` Seth Forshee
2018-06-15 21:09 ` James Bottomley
2018-06-15 21:35 ` Seth Forshee
2018-06-16 3:03 ` James Bottomley
2018-06-18 13:40 ` Seth Forshee
2018-06-18 13:49 ` Amir Goldstein
2018-06-18 14:56 ` James Bottomley
2018-06-18 16:03 ` Seth Forshee
2018-06-18 17:11 ` Amir Goldstein
2018-06-18 19:53 ` Phil Estes
2018-06-21 20:16 ` Seth Forshee
2018-06-24 11:32 ` Amir Goldstein
2018-06-25 11:19 ` Christian Brauner
2018-06-27 7:48 ` James Bottomley
2018-06-27 10:17 ` Amir Goldstein
2018-07-03 16:54 ` Serge E. Hallyn
2018-07-03 17:08 ` Stéphane Graber
2018-07-03 22:05 ` Serge E. Hallyn
2018-06-15 14:54 ` Aleksa Sarai
2018-06-15 15:05 ` Seth Forshee
2018-06-15 15:28 ` James Bottomley
2018-06-15 15:46 ` Seth Forshee
2018-06-15 16:16 ` Christian Brauner
2018-06-15 16:35 ` James Bottomley
2018-06-15 20:17 ` Seth Forshee [this message]
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=20180615201728.GL30028@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christian.brauner@canonical.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tyler.hicks@canonical.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).