From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] autofs - fix log print messages
Date: Thu, 13 Nov 2014 11:50:06 +0800 [thread overview]
Message-ID: <1415850606.2631.19.camel@perseus.themaw.net> (raw)
In-Reply-To: <1415837458.2631.13.camel@perseus.themaw.net>
On Thu, 2014-11-13 at 08:10 +0800, Ian Kent wrote:
> >
> > The tree which these patches were based on seem to have more than a
> > plain rename. For example I get
>
> Right, looks like something has gone missing along the way.
Ahh .. I get it now.
> The tree the patches are against is just a local clone of the Linus tree
> with the patches I'd sent previously applied.
>
> Folding these recent patches into the original series and sending one
> series only that applies on the current Linus tree should sort out the
> problem.
>
> >
> > --- fs/autofs4/autofs_i.h
> > +++ fs/autofs4/autofs_i.h
Looks like the patches I sent on 3rd Dec, which is what Joe commented
on, were missed.
It's probably better for me to start over once its decided how I'll be
sending the patches.
Ian
next prev parent reply other threads:[~2014-11-13 3:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 1:29 [PATCH 1/3] autofs - fix log print messages Ian Kent
2014-11-11 1:30 ` [PATCH 2/3] autofs - change log prints to not insert newline Ian Kent
2014-11-11 1:30 ` [PATCH 3/3] autofs - use pr_xxx() calls directly for logging Ian Kent
2014-11-11 3:25 ` [PATCH 1/3] autofs - fix log print messages Joe Perches
2014-11-11 5:37 ` Ian Kent
2014-11-11 5:49 ` Joe Perches
2014-11-11 6:01 ` Ian Kent
2014-11-12 23:07 ` Andrew Morton
2014-11-13 0:10 ` Ian Kent
2014-11-13 3:50 ` Ian Kent [this message]
2014-11-11 6:07 ` 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=1415850606.2631.19.camel@perseus.themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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