Re: [OSSNA] Intro to kernel hacking tutorial
Hi, On Fri, Jul 5, 2019 at 4:51 AM Tobin C. Harding wrote: > > Hi, > > I am doing a tutorial at OSSNA in San Diego on getting into kernel > hacking. I'm only a couple of years deep into kernel hacking so I > wanted to reach out to those more experienced than myself (and those > less experienced). > > Is there any thing that you would really like to see covered in this > tutorial? > I'm not involved in kernel hacking, but I've tried several times to start writing patches. Because of time sharing issue I haven't get to the end but a tutorial will be great. The question I've asked me during my several tries is where can I be useful (which topics, what I'm confident enough in to play with...). Looking in drivers/staging wasn't any help in my case and making kernel janitor is useful but not very well viewed as I've heard. So I think that digging further in your tutorial on several ways to start kernel hacking may be interesting. > Current format/content: the tutorial will attempt to bridge the gap in > the learning process between the 'first patch' page on kernelnewbies.org > wiki and being 'comfortable' patching the kernel via LKML. Outcome will > (hopefully) be a small patch set into drivers/staging/. (Don't worry > Greg only one group got to this stage last time, you won't get flooded > with patches :) > HTH and very enthusiast to read this tutorial. Loïc > Thanks, > Tobin. > > ___ > Kernelnewbies mailing list > kernelnewb...@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH v2] staging: erofs: add SPDX identifer
Hi Gao, On Mon, Oct 8, 2018 at 4:48 PM Gao Xiang wrote: > > Hi Greg, > > On 2018/10/8 22:43, Greg Kroah-Hartman wrote: > > On Mon, Oct 08, 2018 at 10:36:39PM +0800, Gao Xiang wrote: > >> Hi Greg, > >> > >> On 2018/10/8 22:22, Greg Kroah-Hartman wrote: > >>> Why delete that line? > >>> > >>> But wait, why do we even have this file at all? What's wrong with the > >>> lib/lz4/ code that we have in the kernel today? Shouldn't the code > >>> using these files be moved over to use the lib/ code instead and this > >>> file be deleted? > >> > >> EROFS uses customized LZ4 decompression code for now (which has been > >> offically > >> supported in lz4 1.8.3, I have updated it in > >> https://ozlabs.org/~akpm/mmots/broken-out/lib-lz4-update-lz4-decompressor-module.patch > >> if it is shown up in Linux 4.20, I will remove all the customized LZ4 > >> decompression code), > >> but lib/ code lz4def.h isn't export to include/. > > > > It should show up in 4.20, so you should be able to remove this all > > then. > > Yes, that is correct. I will fix it in 4.20 if the updated LZ4 is already > there. :) So no need to update the patch since the file will be removed. Am I correct? Too bad, I'll make my first patch later... ^^ Thanks Loic > > Thanks, > Gao Xiang > > > > > thanks, > > > > greg k-h > > ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
