[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52F7F486.7040003@roeck-us.net>
Date: Sun, 09 Feb 2014 13:35:02 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Richard Weinberger <richard@....at>,
Paul Bolle <pebolle@...cali.nl>
CC: David Howells <dhowells@...hat.com>,
Koichi Yasutake <yasutake.koichi@...panasonic.com>,
"moderated list:PANASONIC MN10300..." <linux-am33-list@...hat.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 24/28] Remove DEPRECATED
On 02/09/2014 12:04 PM, Richard Weinberger wrote:
> Am 09.02.2014 20:38, schrieb Paul Bolle:
>> On Sun, 2014-02-09 at 19:48 +0100, Richard Weinberger wrote:
>>> The symbol is an orphan, get rid of it.
>>>
>>> Signed-off-by: Richard Weinberger <richard@....at>
>>> ---
>>> arch/mn10300/Kconfig.debug | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/mn10300/Kconfig.debug b/arch/mn10300/Kconfig.debug
>>> index 94efb3e..af18047 100644
>>> --- a/arch/mn10300/Kconfig.debug
>>> +++ b/arch/mn10300/Kconfig.debug
>>> @@ -32,7 +32,7 @@ config KPROBES
>>>
>>> config GDBSTUB
>>> bool "Remote GDB kernel debugging"
>>> - depends on DEBUG_KERNEL && DEPRECATED
>>> + depends on DEBUG_KERNEL
>>
>> But now you've enabled a lot of stuff that, as far as I can tell, could
>> not have been built since v2.6.39.
>
> This is by design. If the code does not build/work it needs to be fixed or removed.
>
I could understand if you would replace DEPRECATED with BROKEN,
but causing a potentially large number of broken builds and
then leave it to others to clean up the resulting mess doesn't
make any sense to me and should, in my opinion, be rejected.
Guenter
--
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