kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: harry198344@gmail.com (wangyubin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to submit for eudyptula-challenge
Date: Tue, 25 Mar 2014 11:08:57 +0800	[thread overview]
Message-ID: <5330F349.5020005@gmail.com> (raw)
In-Reply-To: <CAFSeFg9_5Vw-T65cGPOFprsEqUv=j=9Md8YWEM7ihyTY4b-NSg@mail.gmail.com>

Hi, Aruna

I will use Checkpatch.pl to check my source file by your advice!
thanks again!

Best Regards!
wangyubin

On 03/25/2014 10:48 AM, Aruna Hewapathirane wrote:
> Hi Wangyubin,
>
> There is a *reason* why I decided to give you a helping hand my dear,
>
>   "I" had a very hard time with that task-01 but it did help me
> immensely to begin to understand how things work and are done in the
> kernel. I do not want anyone else to waste time if we can get
> newcomers up to a certain level of competency where they can
> contribute to the kernel this world will be a much better place.
>
> Run checkpatch.pl and try to resolve all errors and warnings before
> you sumbit as else little penguin will say uh-uh sorry try again !
>
> Checkpatch is your friend and so is Google so use them :)
>
>
>
> On Mon, Mar 24, 2014 at 10:42 PM, wangyubin <harry198344@gmail.com> wrote:
>> Hi, Aruna
>>
>> Thanks for your answer!
>>
>> I used printk like this in the previous submit.
>> printk(KERN_ALERT "Hello World !");
>>
>> I will change "KERN_ALERT" to "KERN_DEBUG" and try to submit again!
>>
>> also thanks for Masood Mehmood and Parinay Kondekar's help!
>>
>> Best Regards!
>> wangyubin
>>
>> On 03/25/2014 10:16 AM, Aruna Hewapathirane wrote:
>>> Hi Wangyubin,
>>>
>>> The log level you require is KERN_DEBUG ...
>>>
>>> But when you run checkpatch.pl on your *.c file it will say:
>>>
>>> WARNING: Prefer netdev_dbg(netdev, ... then dev_dbg(dev, ... then
>>> pr_debug(...  to printk(KERN_DEBUG ...
>>>
>>> So replacing printk(KERN_DEBUG ... with pr_debug will resolve this.
>>>
>>> You can find the log files in /var/log and you can list them with ls /var/log.
>>>
>>> The latest kernel I found has the debug and messages logs disabled by
>>> default. You can easily rectify this by editing
>>> /etc/rsyslog.d/50-default.conf. And un-commenting the section :
>>>
>>> #*.=debug;\
>>> #    auth,authpriv.none;\
>>> #   news.none;mail.none    -/var/log/debug
>>> #*.=info;*.=notice;*.=warn;\
>>> #    auth,authpriv.none;\
>>> #    cron,daemon.none;\
>>> #    mail,news.none        -/var/log/messages
>>>
>>> This will give you back the debug and message logs.
>>>
>>> Good luck !
>>>
>>> Aruna
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Mar 24, 2014 at 9:28 PM, wangyubin <harry198344@gmail.com> wrote:
>>>> Hello,
>>>> I have dive into the eudyptula-challenge, but when I submit my result  for task 01.
>>>> I received a reply below:
>>>>> Please print to the kernel debug log level.
>>>> I have sended module(c file), Makefile, and dmesg output for load/unload  the module.
>>>> Could anyone to tell me what does this message mean?
>>>> Thanks a lot!
>>>>
>>>> --
>>>> Best Regards!
>>>> wangyubin
>>>>
>>>>
>>>> _______________________________________________
>>>> Kernelnewbies mailing list
>>>> Kernelnewbies at kernelnewbies.org
>>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2014-03-25  3:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  1:28 How to submit for eudyptula-challenge wangyubin
2014-03-25  1:52 ` Masood Mehmood
2014-12-18  6:02   ` sanjeev sharma
2014-12-18  6:55     ` Fernando Apesteguía
2014-12-18 12:32       ` Best way for PCI memory allocation? testlaster
2014-12-18 15:24         ` John de la Garza
2014-12-18 15:37           ` Nils Holland
2014-12-18  6:58     ` How to submit for eudyptula-challenge Manish Katiyar
2014-12-18  7:09     ` Sudip Mukherjee
2014-12-18 12:32       ` Vinícius Tinti
2014-12-18 12:37         ` Lucas Tanure
2014-12-18 16:22           ` Jessica Ross
2014-12-19  4:30             ` sanjeev sharma
2014-03-25  1:59 ` Parinay Kondekar
2014-03-25  2:16 ` Aruna Hewapathirane
2014-03-25  2:42   ` wangyubin
2014-03-25  2:48     ` Aruna Hewapathirane
2014-03-25  3:08       ` wangyubin [this message]
2014-03-25  3:28         ` Aruna Hewapathirane
2014-03-25  4:47           ` wangyubin
2014-03-25  5:29             ` Pranay Srivastava

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=5330F349.5020005@gmail.com \
    --to=harry198344@gmail.com \
    --cc=kernelnewbies@lists.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).