Garrett D'Amore writes:
> Piotr Jasiukajtis / estibi wrote:
> > Since I hit a little deeper with the changes I have a question...
> > What functions I just shouldn't touch in order to not break the
> > compatibility with drivers?
> >
>
> In general, any *argument* to a function can be made cons
Piotr Jasiukajtis / estibi wrote:
> Garrett D'Amore pisze:
>
>> For someone who wants to get their feet wet in the kernel, an relatively
>> easy task would be to clean up some of the cases where char * is used,
>> but const char * could be used instead.
>>
>> For example, the ddi_log_sysevent(
Piotr Jasiukajtis / estibi pisze:
> Garrett D'Amore pisze:
>> For someone who wants to get their feet wet in the kernel, an relatively
>> easy task would be to clean up some of the cases where char * is used,
>> but const char * could be used instead.
>>
>> For example, the ddi_log_sysevent(), dd
Garrett D'Amore pisze:
> For someone who wants to get their feet wet in the kernel, an relatively
> easy task would be to clean up some of the cases where char * is used,
> but const char * could be used instead.
>
> For example, the ddi_log_sysevent(), ddi_create_minor_node(), and
> similar in
For someone who wants to get their feet wet in the kernel, an relatively
easy task would be to clean up some of the cases where char * is used,
but const char * could be used instead.
For example, the ddi_log_sysevent(), ddi_create_minor_node(), and
similar interfaces take char * arguments, whe
