From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: skinsbursky@virtuozzo.com, criu@openvz.org,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] autofs: show pipe inode in mount options
Date: Tue, 26 Jan 2016 11:55:56 +0800 [thread overview]
Message-ID: <1453780556.3067.15.camel@themaw.net> (raw)
In-Reply-To: <20160125154834.3afe2ede52d0342b61120943@linux-foundation.org>
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
next prev parent reply other threads:[~2016-01-26 3:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 12:02 Stanislav Kinsburskiy
2016-01-07 15:46 ` Stanislav Kinsburskiy
2016-01-08 7:20 ` Ian Kent
2016-01-08 11:29 ` Stanislav Kinsburskiy
2016-01-08 12:58 ` Ian Kent
2016-01-08 15:05 ` Stanislav Kinsburskiy
2016-01-09 1:31 ` Ian Kent
2016-01-11 11:33 ` Stanislav Kinsburskiy
2016-01-22 11:34 ` Stanislav Kinsburskiy
2016-01-23 0:30 ` Ian Kent
2016-01-23 0:57 ` Ian Kent
2016-01-25 11:30 ` Stanislav Kinsburskiy
2016-01-25 23:19 ` Stephen Rothwell
2016-01-25 23:48 ` Andrew Morton
2016-01-26 3:55 ` Ian Kent [this message]
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=1453780556.3067.15.camel@themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome