Introduction and getting started...

Introduction and getting started...

[Darryl L. Pierce]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hi, everybody. I'm fairly new to this mailing list (just signed up last
week) and want to start contributing in some fashion to Linux kernel
development. But I'm not sure where or how to get started. So I'm asking
for some advice: point me to a FAQ or guide for pitching in, please.

Thanks in advance.

-- 
Darryl L. Pierce <mcpierce@gmail.com>
http://mcpierce.multiply.com/
"What do you care what people think, Mr. Feynman?"

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: Introduction and getting started...

[Dan Carpenter]

On Wed, Jul 18, 2012 at 09:31:04AM -0400, Darryl L. Pierce wrote:
> Hi, everybody. I'm fairly new to this mailing list (just signed up last
> week) and want to start contributing in some fashion to Linux kernel
> development. But I'm not sure where or how to get started. So I'm asking
> for some advice: point me to a FAQ or guide for pitching in, please.
> 
> Thanks in advance.

The best way to start is just to fix bugs.  Try compiling the kernel
with the "clang" static checker stuff.  It should find some
potential bugs.  Sort through them and find which are real.  Then
fix them.

I don't think anyone is using the clang checker on a regular basis.

Run it against linux-next.

The key really is to read a lot of code and find bugs.

regards,
dan carpenter

Re: Introduction and getting started...

[Darryl L. Pierce]

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On Wed, Jul 18, 2012 at 04:43:20PM +0300, Dan Carpenter wrote:
> On Wed, Jul 18, 2012 at 09:31:04AM -0400, Darryl L. Pierce wrote:
> > Hi, everybody. I'm fairly new to this mailing list (just signed up last
> > week) and want to start contributing in some fashion to Linux kernel
> > development. But I'm not sure where or how to get started. So I'm asking
> > for some advice: point me to a FAQ or guide for pitching in, please.
> > 
> > Thanks in advance.
> 
> The best way to start is just to fix bugs.  Try compiling the kernel
> with the "clang" static checker stuff.  It should find some
> potential bugs.  Sort through them and find which are real.  Then
> fix them.
> 
> I don't think anyone is using the clang checker on a regular basis.
> 
> Run it against linux-next.
> 
> The key really is to read a lot of code and find bugs.

Thank you, Dan. I'll start there. :)

-- 
Darryl L. Pierce <mcpierce@gmail.com>
http://mcpierce.multiply.com/
"What do you care what people think, Mr. Feynman?"

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]