[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEwNFnDmQZa9gXcKqLXipWSdVfNXszeBWZrc-MDS50A6K0CEww@mail.gmail.com>
Date: Mon, 4 Jun 2012 22:14:28 +0900
From: Minchan Kim <minchan.kim@...il.com>
To: Fengguang Wu <fengguang.wu@...el.com>
Cc: Wanpeng Li <liwp.linux@...il.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
David Howells <dhowells@...hat.com>,
James Morris <james.l.morris@...cle.com>,
Ingo Molnar <mingo@...e.hu>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Wanpeng Li <liwp@...ux.vnet.ibm.com>
Subject: Re: [PATCH] remove no longer use of pdflush interface
On Mon, Jun 4, 2012 at 9:53 PM, Fengguang Wu <fengguang.wu@...el.com> wrote:
> Hi Wanpeng,
>
> On Mon, Jun 04, 2012 at 08:40:42PM +0800, Wanpeng Li wrote:
>> From: Wanpeng Li <liwp@...ux.vnet.ibm.com>
>>
>> remove no longer use of pdflush interface nr_pdflush_threads.
>
> The patch looks good in itself: the nr_pdflush_threads takes no effect
> for many of the recent kernels. But what's the normal process of
> interface removal? Shall we carry some warning printk for some time
> first or whatever?
Yes. you have to add printk warning for noticing it deprecated.
And add descriptoin in Documentation/ABI/obsolete/ and
Documentation/feature-removal-schedule.txt
I don't know how long we maintain it. Is there any rule for it?
Maybe 1-year is suitable, IMHO.
Thanks.
--
Kind regards,
Minchan Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists