How to submit for eudyptula-challenge

[wangyubin]

OK, I will try to use that.
:-)

Best Regards!
wangyubin

On 03/25/2014 11:28 AM, Aruna Hewapathirane wrote:
> Hi Wangyubin,
>
> You may want to drop by the IRC channel : http://kernelnewbies.org/IRC
> has lots of friendly and vastly more experienced folks.
>
>   :)
>
> On Mon, Mar 24, 2014 at 11:08 PM, wangyubin <harry198344 at gmail.com> wrote:
>> 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 at 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 at 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
>>