[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150916200210.GA6341@kroah.com>
Date: Wed, 16 Sep 2015 13:02:10 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Eric Curtin <ericcurtin17@...il.com>
Cc: Austin S Hemmelgarn <ahferroin7@...il.com>,
Steve Calfee <stevecalfee@...il.com>,
Valentina Manea <valentina.manea.m@...il.com>,
shuah.kh@...sung.com, USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: First kernel patch (optimization)
On Wed, Sep 16, 2015 at 05:03:39PM +0100, Eric Curtin wrote:
> Hi Greg,
>
> As I said in the subject of the mail (which I have been since told I
> shouldn't have done this), I'm a noob to kernel code. I tried to pick
> off something super simple to just see what the process of getting a
> patch in is. Youtube videos and documentation only get you so far.
>
> >From reading your response, should I refrain from sending in these
> micro-optimizations in future? Getting in smaller patches is easier
> for me as I only do this in my spare time, which I don't have a lot
> of!
micro-optimizations are great, if you can actually measure them and they
matter :)
If you are looking for someplace to start, might I recommend the
drivers/staging/ directory? I take all sorts of "basic" cleanup
patches, and there are loads of things to do in there. Look at the
drivers/staging/*/TODO files for specific examples of what needs to be
done to get these files cleaned up and fixed properly.
Hope this helps,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists