linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	autofs mailing list <autofs@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 7/7] autofs - change CONFIG_AUTOFS4_FS to CONFIG_AUTOFS_FS
Date: Fri, 05 Jul 2013 17:51:24 +0800	[thread overview]
Message-ID: <1373017884.2497.10.camel@perseus.fritz.box> (raw)
In-Reply-To: <20130701143924.79f57e7206577a2e7777c0a2@canb.auug.org.au>

On Mon, 2013-07-01 at 14:39 +1000, Stephen Rothwell wrote:
> Hi Ian,
> 
> On Mon, 01 Jul 2013 11:14:51 +0800 Ian Kent <raven@themaw.net> wrote:
> >
> > Signed-off-by: Ian Kent <raven@themaw.net>
> 
> Please don't do this.  Find a simple way to make sure that if
> CONFIG_AUTOFS4_FS is set, then "make oldconfig"  (or equivalent) will
> cause CONFIG_AUTOFS_FS to be set the same.

I get what your recommending but still can't think of a way to do it,
any thoughts?

Am I correct that's a +1 for an outright rename of autofs4 to autofs
rather than keeping the autofs4 directory and a compile stub?

I think what I was intending to do (even though I don't really like that
either) isn't apparent since patch 6 didn't make it to the list. I've
re-organized the series since, so perhaps another post of the series to
the list will provoke some suggestions.

> 
> The maintainers will update the defconfigs over time.
> 

Perhaps the maintainers expected the rename to occur a long time ago
(and it probably should have) since after around three years the configs
are still out of date. Still, as you say, it isn't really my place to
fix that.

Ian



  reply	other threads:[~2013-07-05  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  3:14 [RFC PATCH 0/7] autofs4 - rename autofs4 to autofs Ian Kent
2013-07-01  3:14 ` [RFC PATCH 1/7] autofs4 - coding style fixes Ian Kent
2013-07-01  3:14 ` [RFC PATCH 2/7] autofs4 - fix string.h include in auto_dev-ioctl.h Ian Kent
2013-07-01  3:14 ` [RFC PATCH 3/7] autofs4 - move linux/auto_dev-ioctl.h to uapi/linux Ian Kent
2013-07-01  3:14 ` [RFC PATCH 4/7] autofs - merge auto_fs.h and auto_fs4.h Ian Kent
2013-07-01  3:14 ` [RFC PATCH 5/7] autofs - use autofs instead of autofs4 everywhere Ian Kent
2013-07-01  3:14 ` [RFC PATCH 6/7] autofs - rename module autofs4 to autofs Ian Kent
2013-07-01  3:14 ` [RFC PATCH 7/7] autofs - change CONFIG_AUTOFS4_FS to CONFIG_AUTOFS_FS Ian Kent
2013-07-01  4:39   ` Stephen Rothwell
2013-07-05  9:51     ` Ian Kent [this message]
2013-07-08  5:10       ` Stephen Rothwell
2013-07-08  9:11         ` 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=1373017884.2497.10.camel@perseus.fritz.box \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).