public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: TODO list
Date: Fri, 10 Apr 2015 05:34:31 +0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1504100733220.2016@localhost6.localdomain6> (raw)
In-Reply-To: <20100714100136.GA3583@albatros>



On Thu, 9 Apr 2015, Ravi Kerur wrote:

> 
> 
> On 4/9/2015 1:48 AM, Dan Carpenter wrote:
> > On Wed, Apr 08, 2015 at 05:36:01PM -0700, Ravi Kerur wrote:
> >>
> >>
> >> On 4/7/2015 12:49 AM, Dan Carpenter wrote:
> >>> On Fri, Apr 03, 2015 at 01:40:35PM -0700, Ravi Kerur wrote:
> >>>> Team,
> >>>>
> >>>> I am planning to take up following items from TODO list. If it's already picked please let me know. 
> >>>>
> >>>> * pci_set_dma_mask() and friends should use DMA_BIT_MASK(nn) instead of
> >>>>
> >>>> DMA_nnBIT_MASK or 0xffff... This is not 2.4 compatible, so beware of drivers with same code. [D: http://marc.theaimsgroup.com/?t\x108001993000001] Don't forget to #include dma-mapping.h
> >>>>
> >>>> * check kmallocs for things like GFP_DMA without a memtype. 
> >>>>
> >>>
> >>> The TODO is desperately out of date.  No one cares about 2.4 at all.
> >>> These days we don't really allow drivers to have backwards compatability
> >>> code so they compile on old kernels.  That stuff has to be stored out of
> >>> the main kernel tree.  We also have the compat-wireless and other
> >>> similar ways of backporting drivers.
> >>
> >> Thanks Dan. Do you recommend anything else for contribution? I am not a
> >> newbie to kernel but never contributed to kernel before so any inputs
> >> appreciated.
> > 
> > There is always stuff to fix in staging.  It's at all levels of
> > difficulty.
> 
> Can you please point me to the link or anything which lists what needs to be done. I can pick some of it.

You can run checkpatch, or other tools and fix the things that they 
highlight.  Once you start really looking at the code, you are likely to 
see other things that can be improved as well.  Some staging drivers also 
have TODO lists.

julia

  parent reply	other threads:[~2015-04-10  5:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 10:01 TODO list Kulikov Vasiliy
2012-07-08 13:38 ` TODO List Benjamin BEURDOUCHE
2012-07-09  0:51 ` Keith Woodie
2015-04-03 20:40 ` TODO list Ravi Kerur
2015-04-07  7:49 ` Dan Carpenter
2015-04-09  0:36 ` Ravi Kerur
2015-04-09  8:48 ` Dan Carpenter
2015-04-09 22:57 ` Ravi Kerur
2015-04-10  5:34 ` Julia Lawall [this message]
2015-04-10 22:47 ` Ravi Kerur
2015-04-11  5:17 ` Julia Lawall
2015-04-13 22:02 ` Dan Carpenter
2015-04-13 22:42 ` Ravi Kerur
2015-04-14  6:58 ` Dan Carpenter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1504100733220.2016@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox