From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: Daniel Rodrick <daniel.rodrick@gmail.com>,
kernelnewbies <kernelnewbies@nl.linux.org>,
Linux Newbie <linux-newbie@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: after effects of a kernel API change
Date: Thu, 18 Jan 2007 11:44:11 +0200 [thread overview]
Message-ID: <20070118094411.GB29695@Ahmed> (raw)
In-Reply-To: <b115cb5f0701172135k411dca56u92101a929799548a@mail.gmail.com>
On Thu, Jan 18, 2007 at 11:05:53AM +0530, Rajat Jain wrote:
> >>
> >> Is there any way volunteers like me can help in this exercise?
> >
> >See the /APIchanges in the Kernel Janitors TODO list
> >http://kernelnewbies.org/KernelJanitors/Todo
> >
> [...]
> 1) How do I make sure if some one is NOT working on any of the
> mentioned bullet points? Who coordinates? On what mailing list?
Check latest trees to make sure the work is not duplicated. espicially
trees like -mm and subsystem ones.
> 2) Do any patches for the above Todo list have the chances of getting
> merged into the mainstream kernel? Who approves? I suppose the
> respective maintainer of the driver / subsystem getting affected?
I advise lurking (following/reading) the list for at least 2 or 3 weeks and
you'll automatically understand how the "system" works. Also check:
$KERNEL_TREE/Documentation/HOWTO
$KERNEL_TREE/Documentation/SubmittingPatches
$KERNEL_TREE/Documentation/CodingStyle
--
Ahmed S. Darwish
http://darwish-07.blogspot.com
prev parent reply other threads:[~2007-01-18 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 4:15 after effects of a kernel API change Daniel Rodrick
2007-01-18 5:04 ` Greg KH
2007-01-18 5:10 ` Ahmed S. Darwish
2007-01-18 5:35 ` Rajat Jain
2007-01-18 7:47 ` Eric W. Biederman
2007-01-18 9:44 ` Ahmed S. Darwish [this message]
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=20070118094411.GB29695@Ahmed \
--to=darwish.07@gmail.com \
--cc=daniel.rodrick@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rajat.noida.india@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).