[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfuBxztMMUrbUvVft8gXB4Jk2yi+AXVV-TVLXAFdtgMf4AUgg@mail.gmail.com>
Date: Fri, 23 Mar 2012 18:12:51 -0600
From: Jim Cromie <jim.cromie@...il.com>
To: Jason Baron <jbaron@...hat.com>
Cc: rusty@...tcorp.com.au, linux-kernel@...r.kernel.org
Subject: Re: [00/11] pr_debug during module initialization
On Fri, Mar 23, 2012 at 2:27 PM, Jason Baron <jbaron@...hat.com> wrote:
> On Wed, Mar 14, 2012 at 05:01:55PM -0600, jim.cromie@...il.com wrote:
>> This is 3rd revision of the dyndbg modinit patches, previously sent
>> Dec 11. Patches 1-17/25 sent then were added to driver-core-next,
>> this set reworks the remainder.
>>
>> It implements the "fake" module param approach proposed by
>> Thomas Renninger, back in https://lkml.org/lkml/2010/9/15/397
>>
>
> Hi,
>
> I'm wondering, if we leave the cmdline parameter: 'ddebug_query=' around
> for a bit before removing it, so it doesn't get dropped too suddenly.
> Perhaps, we add a warning msg, for people that are still using it
> for a few releases warning that it is deprecated, before dropping it.
>
OK, thats reasonable. I'll explicitly deprecate it in
Doc/feature-removal-schedule. What is the default
deprecation time, 2 releases ?
Assuming this patchset is for 3.4, I'll say 3.6 unless someone disagrees.
> Also, let's add the 'dyndbg=' syntax to Documentation/kernel-parameters.txt.
>
oops. that got dropped accidentally.
> A previous version had a build-time error if a module used 'dyndbg' as a
> module param - why did that get dropped?
Rusty expressed view that if developers add it, they meant it.
He also said the macro was redundant with another,
but I didnt look further cuz of the 1st point.
>
> Thanks!
>
> -Jason
--
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