On Feb 5, 2008 2:18 AM, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 30 Jan 2008 17:41:03 -0500 Jeff Layton <[EMAIL PROTECTED]> wrote:
>
> > I have no problem with targeting smbfs for removal, but I thought
> > Andrew had an unofficial policy that we should first mark things to be
> > deprecated, and then remove them 2 releases later. That seems like a
> > sensible policy to me. If we mark it deprecated in 2.6.25 then we can
> > remove it after 2.6.26 is released.
> >
> > It might not even hurt to have a nice loud printk when the smbfs
> > module is plugged in to warn users that it's slated to be removed,
> > and that they should move to CIFS as soon as possible.
> From: Andrew Morton <[EMAIL PROTECTED]>
>
> smbfs is a bit buggy and has no maintainer. Change it to shout at the user on
> the first five mount attempts - tell them to switch to CIFS.
>
> Come December we'll mark it BROKEN and see what happens.
>
> + if (warn_count < 5) {
> + warn_count++;
> + printk(KERN_EMERG "smbfs is deprecated and will be removed in"
> + " December, 2006. Please migrate to cifs\n");
> + }
>
> if (!raw_data)
> goto out_no_data;
> _
>
>
> queued for over 1.5 years waiting for the go-ahead from Steve.
>
> It looks like it's time? If so, what should I set the date to?
If the 2.6.26 cycle would starts in April, then saying April 2008 is
fine with me.
--
Thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
