kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Denis Kirjanov <dkirjanov@suse.de>
To: A mp <ampklabs@gmail.com>, kernelnewbies@kernelnewbies.org
Subject: Re: pr_info in driver question
Date: Wed, 6 Jul 2022 10:53:12 +0300	[thread overview]
Message-ID: <06f10c25-0492-2b6f-3807-7c5199f15dc1@suse.de> (raw)
In-Reply-To: <20220706064736.lhsjwf3yrpjwquuz@mycloud>



On 7/6/22 09:47, A mp wrote:
> Hi everyone,
> 
> My name is Andrew.
> 
> Recently, I went through the Linux Foundations intro to kernel development course. As part of the course, it gets us to put a print statement inside of the uvcvideo driver, recompile the kernel and then load the module and check dmesg for the print statement.
> 
> After several attempts, I was unable to find this print statement inside of dmesg. I know that the modified drier was compiling successfully and my custom kernel was indeed installed but no idea about this pr_info statement.
> 
> I tried this in Ubuntu and Fedora inside of virtualbox. Not sure if that would make any difference.

echo "7" > /proc/sys/kernel/printk

and make sure that you have your module listed in lsmod

> 
> Thanks,
> 
> Andrew.
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2022-07-06  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  6:47 pr_info in driver question A mp
2022-07-06  7:53 ` Denis Kirjanov [this message]
     [not found]   ` <20220706075833.h7v7krobysyxqnat@mycloud>
2022-07-06  8:32     ` Denis Kirjanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06f10c25-0492-2b6f-3807-7c5199f15dc1@suse.de \
    --to=dkirjanov@suse.de \
    --cc=ampklabs@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).