Krzysztof Kozlowski writes:
> On 03/04/2024 15:50, Kalle Valo wrote:
>
>> Jeff Johnson writes:
>>
>>> On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
This driver's initialization functions do not perform any custom code,
except printing messages. Printing messages on modules
On 03/04/2024 15:50, Kalle Valo wrote:
> Jeff Johnson writes:
>
>> On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
>>> This driver's initialization functions do not perform any custom code,
>>> except printing messages. Printing messages on modules
>>> loading/unloading is discouraged because
On 03/04/2024 15:50, Kalle Valo wrote:
> Jeff Johnson writes:
>
>> On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
>>> This driver's initialization functions do not perform any custom code,
>>> except printing messages. Printing messages on modules
>>> loading/unloading is discouraged because
Jeff Johnson writes:
> On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
>> This driver's initialization functions do not perform any custom code,
>> except printing messages. Printing messages on modules
>> loading/unloading is discouraged because it pollutes the dmesg
>> regardless whether
On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
> This driver's initialization functions do not perform any custom code,
> except printing messages. Printing messages on modules
> loading/unloading is discouraged because it pollutes the dmesg
> regardless whether user actually has this device.
This driver's initialization functions do not perform any custom code,
except printing messages. Printing messages on modules
loading/unloading is discouraged because it pollutes the dmesg
regardless whether user actually has this device. Core kernel code
already gives tools to investigate
