Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1314920 > unrolled thread

Re: [PATCH] autofs: show pipe inode in mount options

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] autofs: show pipe inode in mount options Stanislav Kinsburskiy <skinsbursky@odin.com> - 2016-01-22 12:40 +0100
    Re: [PATCH] autofs: show pipe inode in mount options Ian Kent <raven@themaw.net> - 2016-01-23 01:40 +0100
      Re: [PATCH] autofs: show pipe inode in mount options Ian Kent <raven@themaw.net> - 2016-01-23 02:00 +0100
      Re: [PATCH] autofs: show pipe inode in mount options Stanislav Kinsburskiy <skinsbursky@odin.com> - 2016-01-25 12:40 +0100
      Re: [PATCH] autofs: show pipe inode in mount options Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-26 00:20 +0100
        Re: [PATCH] autofs: show pipe inode in mount options Andrew Morton <akpm@linux-foundation.org> - 2016-01-26 00:50 +0100
          Re: [PATCH] autofs: show pipe inode in mount options Ian Kent <raven@themaw.net> - 2016-01-26 05:00 +0100

#1314920 — Re: [PATCH] autofs: show pipe inode in mount options

Hi again,

I would like to ask about any progress with this patch?
Any other requirements to make it able to merge?

[toc] | [next] | [standalone]

#1315466

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

[toc] | [prev] | [next] | [standalone]

#1315474

On Sat, 2016-01-23 at 08:30 +0800, Ian Kent wrote:
> 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).

Apologies, there appears to be a parse error in my grammar above,
sorry, and clearly "push" should be "pull" in the paragraph above.

> 
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe autofs" in

[toc] | [prev] | [next] | [standalone]

#1316531

23.01.2016 01:30, Ian Kent пишет:
> 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?

No, you didn't.
I have send it few minutes ago.
Thanks.

> Ian

[toc] | [prev] | [next] | [standalone]

#1317398

Hi Ian,

On Sat, 23 Jan 2016 08:30:17 +0800 Ian Kent <raven@themaw.net> wrote:
>
> 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 guess if its just a few patches every now and then, then Andrew
Morton may be the best person to shepherd them upstream.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[toc] | [prev] | [next] | [standalone]

#1317412

On Tue, 26 Jan 2016 10:19:07 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Ian,
> 
> On Sat, 23 Jan 2016 08:30:17 +0800 Ian Kent <raven@themaw.net> wrote:
> >
> > 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 guess if its just a few patches every now and then, then Andrew
> Morton may be the best person to shepherd them upstream.

yup, send 'em along.

I actually was handling the autofs4 stuff back in 2014 for a bit.

[toc] | [prev] | [next] | [standalone]

#1317513

On Mon, 2016-01-25 at 15:48 -0800, Andrew Morton wrote:
> On Tue, 26 Jan 2016 10:19:07 +1100 Stephen Rothwell <
> sfr@canb.auug.org.au> wrote:
> 
> > Hi Ian,
> > 
> > On Sat, 23 Jan 2016 08:30:17 +0800 Ian Kent <raven@themaw.net>
> > wrote:
> > > 
> > > 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 guess if its just a few patches every now and then, then Andrew
> > Morton may be the best person to shepherd them upstream.
> 
> yup, send 'em along.
> 
> I actually was handling the autofs4 stuff back in 2014 for a bit.

Thanks Andrew.

Last time I tried to send the module rename series we got confused some
how, patches not seen leading to conflicts in applying later patches
IIRC, which lead to the recommendation I send them to linux-next.

The series has grown a bit too now but I'm thinking I should send them
in smaller groups, such as coding style fixes and white space fixes,
change to use pr* logging, etc.

Hopefully that will make the process much more straight forward.

The thing is the patches are mostly not urgent which is why I keep
postponing sending them when higher priority things come up.

As for the patch from Stanislav, I'll put that at the top of my patch
queue, have a quick look at it and send it over so that, hopefully, it
can get merged.

I'll probably send a couple of others too to get things going on with
(what I'm calling) the module rename series.

Ian

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web