All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: skinsbursky@virtuozzo.com
Cc: criu@openvz.org, autofs@vger.kernel.org,
	linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] autofs: show pipe inode in mount options
Date: Sat, 23 Jan 2016 08:30:17 +0800	[thread overview]
Message-ID: <1453509017.3042.7.camel@themaw.net> (raw)
In-Reply-To: <56A213CA.5090704@odin.com>

On Fri, 2016-01-22 at 12:34 +0100, Stanislav Kinsburskiy wrote:
> Hi again,
> 
> I would like to ask about any progress with this patch?
> Any other requirements to make it able to merge?

Sorry for the delay.

Since there haven't been any comments from Al or Stephen I'm think I
should include it in the series I plan on sending to linux-next to
rename autofs4 to autofs (among other things).

I haven't had anything significant enough for autofs to warrant
maintaining a tree and sending push requests so I'll need to ask
Stephen what I need to do (perhaps you could offer some advise on that
now Stephen, please).

I'm also struggling to get back to this and carry out the needed
testing and I'll need to re-base the series too now but I'm getting
there.

I didn't see a follow up patch with an updated description, did I miss
it?

Ian

  reply	other threads:[~2016-01-23  0:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 12:02 [PATCH] autofs: show pipe inode in mount options Stanislav Kinsburskiy
2016-01-07 15:46 ` Stanislav Kinsburskiy
2016-01-07 15:46   ` Stanislav Kinsburskiy
2016-01-08  7:20   ` Ian Kent
2016-01-08  7:20     ` Ian Kent
2016-01-08 11:29     ` Stanislav Kinsburskiy
2016-01-08 11:29       ` Stanislav Kinsburskiy
2016-01-08 12:58       ` Ian Kent
2016-01-08 12:58         ` Ian Kent
2016-01-08 15:05         ` Stanislav Kinsburskiy
2016-01-08 15:05           ` Stanislav Kinsburskiy
2016-01-09  1:31           ` Ian Kent
2016-01-09  1:31             ` Ian Kent
2016-01-11 11:33             ` Stanislav Kinsburskiy
2016-01-11 11:33               ` Stanislav Kinsburskiy
2016-01-22 11:34               ` Stanislav Kinsburskiy
2016-01-22 11:34                 ` Stanislav Kinsburskiy
2016-01-23  0:30                 ` Ian Kent [this message]
2016-01-23  0:57                   ` Ian Kent
2016-01-25 11:30                   ` Stanislav Kinsburskiy
2016-01-25 11:30                     ` Stanislav Kinsburskiy
2016-01-25 23:19                   ` Stephen Rothwell
2016-01-25 23:48                     ` Andrew Morton
2016-01-25 23:48                       ` Andrew Morton
2016-01-26  3:55                       ` Ian Kent
2016-01-26  3:55                         ` Ian Kent
2016-02-02  4:43                         ` Ian Kent
2016-02-02  4:43                           ` Ian Kent

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=1453509017.3042.7.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=criu@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=skinsbursky@virtuozzo.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 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.