I have the same situation. Seems that Eudyptula maintainers forget about us )))... 08.08.2016, 12:14, "Madhu K" <madhu.sk89@xxxxxxxxx>: > Hi Saket Sinha, > > I am also kernel newbie, I started Eucalyptula challenge challenge 4 months back, till now I have completed 4 tasks and submitted result for 5th task two months back, till now I have not received any response from little. > > So during this time I wanted occupy with other kernel stuff, can please share how to proceed with "TODOs in the staging area drive" you mentioned below.It will be more helpful for me and other newbies to involve in kernel development activity. > > Thanks®ards, > Madhu > > On Sun, Aug 7, 2016 at 8:24 PM, <kernelnewbies-request@xxxxxxxxxxxxxxxxx> wrote: >> Send Kernelnewbies mailing list submissions to >> kernelnewbies@xxxxxxxxxxxxxxxxx >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> or, via email, send a message with subject or body 'help' to >> kernelnewbies-request@xxxxxxxxxxxxxxxxx >> >> You can reach the person managing the list at >> kernelnewbies-owner@xxxxxxxxxxxxxxxxx >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Kernelnewbies digest..." >> >> Today's Topics: >> >> 1. one more new Bie (Anurag Ranjan) >> 2. Re: one more new Bie (Saket Sinha) >> 3. Re: one more new Bie (Fran?ois) >> 4. Re: one more new Bie (Giedrius Statkevi?ius) >> 5. Linux Coding style template (Charls D. Chap) >> 6. Re: Linux Coding style template (Greg KH) >> 7. Re: Are these books outdated? (John Chludzinski) >> 8. Re: Linux Coding style template (Charls D. Chap) >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sat, 6 Aug 2016 21:43:47 +0530 >> From: Anurag Ranjan <anurag.eee@xxxxxxxxx> >> Subject: one more new Bie >> To: kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: >> <CANeted3zQ8vMbk4Nzk77OSz8jaPFRB28bymJh-egSg-SCRcerA@xxxxxxxxxxxxxx> >> Content-Type: text/plain; charset="utf-8" >> >> Hi All, >> >> I am new to this list. Please help me with any new bie helper guide. >> >> How do we get work assigned here? or this is just a query forum. >> >> Regards, >> Anurag >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160806/d52945b7/attachment-0001.html >> >> ------------------------------ >> >> Message: 2 >> Date: Sat, 6 Aug 2016 21:54:59 +0530 >> From: Saket Sinha <saket.sinha89@xxxxxxxxx> >> Subject: Re: one more new Bie >> To: Anurag Ranjan <anurag.eee@xxxxxxxxx> >> Cc: kernelnewbies <kernelnewbies@xxxxxxxxxxxxxxxxx> >> Message-ID: >> <CAK25hWN6Pets=e9HDFTyah9LF6CkB8gXX50JNLjmwG1wd-tb1g@xxxxxxxxxxxxxx> >> Content-Type: text/plain; charset="utf-8" >> >> Hi Anurag, >> >> Welcome to the list. This is a query forum but we can surely help you with >> getting started. >> >> Take up Eucalyptus challenge or the TODOs in the staging area driver if >> you're interested in kernel development. >> >> Let me know if you're looking for something specific. >> >> Regards, >> Saket Sinha >> >> On 06-Aug-2016 9:47 PM, "Anurag Ranjan" <anurag.eee@xxxxxxxxx> wrote: >> >>> Hi All, >>> >>> I am new to this list. Please help me with any new bie helper guide. >>> >>> How do we get work assigned here? or this is just a query forum. >>> >>> Regards, >>> Anurag >>> >>> _______________________________________________ >>> Kernelnewbies mailing list >>> Kernelnewbies@xxxxxxxxxxxxxxxxx >>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >>> >>> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160806/7be1684e/attachment-0001.html >> >> ------------------------------ >> >> Message: 3 >> Date: Sat, 6 Aug 2016 18:48:28 +0200 >> From: Fran?ois <fser@xxxxxxxxxxxxxx> >> Subject: Re: one more new Bie >> To: kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: <20160806164827.hf7wzw6wkzw5flb5@sith> >> Content-Type: text/plain; charset=iso-8859-1 >> >> On Sat, Aug 06, 2016 at 09:54:59PM +0530, Saket Sinha wrote: >>> Hi Anurag, >>> >>> Welcome to the list. This is a query forum but we can surely help you with >>> getting started. >>> >>> Take up Eucalyptus challenge or the TODOs in the staging area driver if >>> you're interested in kernel development. >> >> I think you're talking about eudyptula [1], unfortunayelly, it seems that little >> has been out of business for quite a while now. >> >> [1] http://eudyptula-challenge.org/ >> >> @Anurag: welcome here :) >> >> -- >> Fran?ois >> >> ------------------------------ >> >> Message: 4 >> Date: Sat, 6 Aug 2016 20:02:28 +0300 >> From: Giedrius Statkevi?ius <giedrius.statkevicius@xxxxxxxxx> >> Subject: Re: one more new Bie >> To: Saket Sinha <saket.sinha89@xxxxxxxxx> >> Cc: Anurag Ranjan <anurag.eee@xxxxxxxxx>, kernelnewbies >> <kernelnewbies@xxxxxxxxxxxxxxxxx> >> Message-ID: <20160806170228.GB20321@tyrael> >> Content-Type: text/plain; charset=us-ascii >> >> Hi Saket, >> >> On Sat, Aug 06, 2016 at 09:54:59PM +0530, Saket Sinha wrote: >>> Hi Anurag, >>> >>> Welcome to the list. This is a query forum but we can surely help you with >>> getting started. >>> >>> Take up Eucalyptus challenge or the TODOs in the staging area driver if >>> you're interested in kernel development. >>> >>> Let me know if you're looking for something specific. >>> >>> Regards, >>> Saket Sinha >> >> Heh... it's called the eudyptula challenge, not the eucalyptus challenge. Also, >> please don't top-post. >> >> A: Because this is annoying >> Q: Why? >> >>> >>> On 06-Aug-2016 9:47 PM, "Anurag Ranjan" <anurag.eee@xxxxxxxxx> wrote: >>> >>> > Hi All, >>> > >>> > I am new to this list. Please help me with any new bie helper guide. >>> > >>> > How do we get work assigned here? or this is just a query forum. >>> > >>> > Regards, >>> > Anurag >>> > >> >> -- >> Giedrius >> >> ------------------------------ >> >> Message: 5 >> Date: Sun, 7 Aug 2016 00:22:03 +0300 >> From: "Charls D. Chap" <chapcharls@xxxxxxxxx> >> Subject: Linux Coding style template >> To: kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: >> <CAA6eV_ThVicvXa_c+EKH_gVMrm57OEKoKeAK65J5Z7d=+WykkQ@xxxxxxxxxxxxxx> >> Content-Type: text/plain; charset=UTF-8 >> >> I want to transform some C source files. following Linux kernel coding style. >> >> - Does script/Lindent STRICTLY follows all linux kernel coding style rules? >> - What scripts/templates do you use/suggest for elegant code style >> with the fact that >> we are talking about Linux Kernel Coding? >> >> The GNU guys suggest indent with the following parameters: >> -nbad -bap -nbc -bbo -hnl -br -brs -c33 -cd33 -ncdb -ce -ci4 >> -cli0 -d0 -di1 -nfc1 -i8 -ip0 -l80 -lp -npcs -nprs -npsl -sai >> -saf -saw -ncs -nsc -sob -nfca -cp33 -ss -ts8 -il1 >> >> On the other hand: >> Linux/script/Lindent contains: >> -npro -kr -i8 -ts8 -sob -l80 -ss -ncs -cp1 >> >> Differences so far: >> 1) >> indent with gnu parameters inserts a space on labels eg. >> err: vs >> err: >> >> 2) >> indent with gnu parameters inserts 26 spaces >> #endif /* >> something like this*/ >> >> So probably gnu site is outdated? >> >> Also, I have noticed that they both fail theyto leave the empty line >> of a label empty >> For example, err: code >> to >> err: >> code >> >> What does the coding style suggests in this case? >> >> Have you found, other cases such the above? >> >> ------------------------------ >> >> Message: 6 >> Date: Sun, 7 Aug 2016 06:39:48 +0200 >> From: Greg KH <greg@xxxxxxxxx> >> Subject: Re: Linux Coding style template >> To: "Charls D. Chap" <chapcharls@xxxxxxxxx> >> Cc: kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: <20160807043948.GA7711@xxxxxxxxx> >> Content-Type: text/plain; charset=us-ascii >> >> On Sun, Aug 07, 2016 at 12:22:03AM +0300, Charls D. Chap wrote: >>> I want to transform some C source files. following Linux kernel coding style. >>> >>> - Does script/Lindent STRICTLY follows all linux kernel coding style rules? >>> - What scripts/templates do you use/suggest for elegant code style >>> with the fact that >>> we are talking about Linux Kernel Coding? >>> >>> >>> The GNU guys suggest indent with the following parameters: >>> -nbad -bap -nbc -bbo -hnl -br -brs -c33 -cd33 -ncdb -ce -ci4 >>> -cli0 -d0 -di1 -nfc1 -i8 -ip0 -l80 -lp -npcs -nprs -npsl -sai >>> -saf -saw -ncs -nsc -sob -nfca -cp33 -ss -ts8 -il1 >>> >>> On the other hand: >>> Linux/script/Lindent contains: >>> -npro -kr -i8 -ts8 -sob -l80 -ss -ncs -cp1 >>> >>> Differences so far: >>> 1) >>> indent with gnu parameters inserts a space on labels eg. >>> err: vs >>> err: >>> >>> 2) >>> indent with gnu parameters inserts 26 spaces >>> #endif /* >>> something like this*/ >>> >>> >>> So probably gnu site is outdated? >> >> Probably, start with running Lindent, and then fix up the mess it leaves >> by hand. Shouldn't take more than a day to do it. >> >> good luck! >> >> greg k-h >> >> ------------------------------ >> >> Message: 7 >> Date: Sun, 07 Aug 2016 09:29:01 -0400 >> From: John Chludzinski <john.chludzinski@xxxxxxxxxxx> >> Subject: Re: Are these books outdated? >> To: Aleksander Alekseev <afiskon@xxxxxxxxx> >> Cc: Kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: <156b7e5e8149927ea9f25e2c12d46aac@xxxxxxxxxxxxxxxx> >> Content-Type: text/plain; charset=US-ASCII; format=flowed >> >> Linux Kernel Development by Robert Love >> >> On 2016-07-14 07:01, Aleksander Alekseev wrote: >>> Hello >>> >>> I'm a full-time *nix C developer. I have a pretty good idea how >>> operating systems work. Still I would like learn more about Linux >>> internals in particular, write a few device drivers, maybe some >>> patches to kernel itself, etc. Here are a few books I've found: >>> >>> * Linux Kernel Development, 3rd Edition (2010) >>> * Understanding the Linux Kernel, 3rd Edition (2005) >>> * Linux Device Drivers, 3rd Edition (2005) >>> >>> Could you tell me please, are these books considered worth reading in >>> year 2016 or they are completely out of date? Perhaps there are some >>> newer books and/or tutorials you could recommend? >> >> ------------------------------ >> >> Message: 8 >> Date: Sun, 7 Aug 2016 17:53:15 +0300 >> From: "Charls D. Chap" <chapcharls@xxxxxxxxx> >> Subject: Re: Linux Coding style template >> To: Greg KH <greg@xxxxxxxxx> >> Cc: kernelnewbies@xxxxxxxxxxxxxxxxx >> Message-ID: >> <CAA6eV_RiN0wZKA12PKHHiR3s5gzgj7p56Q4Td4qGS+WYN+ohiw@xxxxxxxxxxxxxx> >> Content-Type: text/plain; charset=UTF-8 >> >> On Sun, Aug 7, 2016 at 7:39 AM, Greg KH <greg@xxxxxxxxx> wrote: >>> On Sun, Aug 07, 2016 at 12:22:03AM +0300, Charls D. Chap wrote: >>>> I want to transform some C source files. following Linux kernel coding style. >> >> My questions are more generic, i am interesting in an automatic way for >> identation! And also, i am interesting to what kernel developers will >> do in the following cases, so i am forwarding again the email. >> >> please take a look to this example >> width is 90, what a kernel developer will do? spliti in two lines, or >> leave it us it is, >> cause i think it's more readable, in this way >> qq->run = mmap(NULL, mmap_size, PROT_READ | PROT_WRITE, MAP_SHARED, >> qq->vcpu, 0); >> >> Also, have you find a way to tell indent not to indent, struct definitions? >> In .h, when you have a huge structure definition, it's more readable, >> to have it's struct friend one below the other, aligned! >> struct kvm_mem_bank { >> struct list_head list; >> u64 guest_phys_addr; >> void *host_addr; >> u64 size; >> }; >> >> This also counts for variables initiliazation >> int x = 0 >> char *dog = animal->dog->name; >> char *cat = animal->cat->name; >> char * elephant = animal->elephant->name; >> >> Any ideas? >> >> - Does script/Lindent STRICTLY follows all linux kernel coding style rules? >> - What scripts/templates do you use/suggest for elegant code style >> with the fact that >> we are talking about Linux Kernel Coding? >> >> The GNU guys suggest indent with the following parameters: >> -nbad -bap -nbc -bbo -hnl -br -brs -c33 -cd33 -ncdb -ce -ci4 >> -cli0 -d0 -di1 -nfc1 -i8 -ip0 -l80 -lp -npcs -nprs -npsl -sai >> -saf -saw -ncs -nsc -sob -nfca -cp33 -ss -ts8 -il1 >> >> On the other hand: >> Linux/script/Lindent contains: >> -npro -kr -i8 -ts8 -sob -l80 -ss -ncs -cp1 >> >> Differences so far: >> 1) >> indent with gnu parameters inserts a space on labels eg. >> err: vs >> err: >> >> 2) >> indent with gnu parameters inserts 26 spaces >> #endif /* >> something like this */ >> >> So probably gnu site is outdated? >> >> Also, I have noticed that they both fail theyto leave the empty line >> of a label empty >> For example, err: code >> to >> err: >> code >> >> What does the coding style suggests in this case? >> >> Have you found, other cases such the above? >> >> ------------------------------ >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies@xxxxxxxxxxxxxxxxx >> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> >> End of Kernelnewbies Digest, Vol 69, Issue 11 >> ********************************************* > > , > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
