* From which tree can I start Linux kernel development
@ 2012-06-28 16:01 Sannu K
2012-06-28 21:14 ` Ezequiel Garcia
0 siblings, 1 reply; 4+ messages in thread
From: Sannu K @ 2012-06-28 16:01 UTC (permalink / raw)
To: kernelnewbies
Hi All,
I would like to contribute to linux kernel. I have gone through the
coding style used and other stuffs. I would like to plunge into kernel
development. To do that should I start with linux-next git tree?
Please let me know whether the following procedure is correct:
1. Clone linux-next tree.
2. Make modifications.
3. Create patch and check it against checkpatch.pl.
4. Mail patch to the maintainers.
5. Get the patches reviewed and do necessary changes. Do step 4 and
step5 as many time as necessary.
6. Patch gets merges into kernel.
I would like to work on stuff related to graphics or video. Is there any
small task that I could start with? Please provide some pointers and
suggestions.
Thanks,
Sannu
^ permalink raw reply [flat|nested] 4+ messages in thread
* From which tree can I start Linux kernel development
2012-06-28 16:01 From which tree can I start Linux kernel development Sannu K
@ 2012-06-28 21:14 ` Ezequiel Garcia
2012-06-29 14:32 ` Sannu K
[not found] ` <FB112703C4930F4ABEBB5B763F96491139378F21@MAILSERV2A.lorien.fkie.fgan.de>
0 siblings, 2 replies; 4+ messages in thread
From: Ezequiel Garcia @ 2012-06-28 21:14 UTC (permalink / raw)
To: kernelnewbies
On Thu, Jun 28, 2012 at 1:01 PM, Sannu K <sannumail4foss@gmail.com> wrote:
> Hi All,
>
> I would like to contribute to linux kernel. I have gone through the
> coding style used and other stuffs. I would like to plunge into kernel
> development. To do that should I start with linux-next git tree?
>
> Please let me know whether the following procedure is correct:
> 1. Clone linux-next tree.
> 2. Make modifications.
> 3. Create patch and check it against checkpatch.pl.
> 4. Mail patch to the maintainers.
> 5. Get the patches reviewed and do necessary changes. Do step 4 and
> step5 as many time as necessary.
> 6. Patch gets merges into kernel.
>
> I would like to work on stuff related to graphics or video. Is there any
> small task that I could start with? Please provide some pointers and
> suggestions.
>
That's more or less right. Don't forget linux-next cant't rebased
because every day a new git tree is created. This is important
when rebasing commits.
There are also subsystem trees you can pickup to do development.
Just to name a few:
- alsa
- media
- m68k arch
all have a git tree to work. You can find them on git.kernel.org.
Also:
- kernel people hate top-posting
- kernel people hate non-text mail
- learn git
- read Documentation/SubmittingPatches **carefully**
- watch gregkh [1]
http://www.youtube.com/watch?v=LLBrBBImJt4
Good luck,
Ezequiel.
^ permalink raw reply [flat|nested] 4+ messages in thread
* From which tree can I start Linux kernel development
2012-06-28 21:14 ` Ezequiel Garcia
@ 2012-06-29 14:32 ` Sannu K
[not found] ` <FB112703C4930F4ABEBB5B763F96491139378F21@MAILSERV2A.lorien.fkie.fgan.de>
1 sibling, 0 replies; 4+ messages in thread
From: Sannu K @ 2012-06-29 14:32 UTC (permalink / raw)
To: kernelnewbies
On Thu, 2012-06-28 at 18:14 -0300, Ezequiel Garcia wrote:
> On Thu, Jun 28, 2012 at 1:01 PM, Sannu K <sannumail4foss@gmail.com> wrote:
> > Hi All,
> >
> > I would like to contribute to linux kernel. I have gone through the
> > coding style used and other stuffs. I would like to plunge into kernel
> > development. To do that should I start with linux-next git tree?
> >
> > Please let me know whether the following procedure is correct:
> > 1. Clone linux-next tree.
> > 2. Make modifications.
> > 3. Create patch and check it against checkpatch.pl.
> > 4. Mail patch to the maintainers.
> > 5. Get the patches reviewed and do necessary changes. Do step 4 and
> > step5 as many time as necessary.
> > 6. Patch gets merges into kernel.
> >
> > I would like to work on stuff related to graphics or video. Is there any
> > small task that I could start with? Please provide some pointers and
> > suggestions.
> >
>
> That's more or less right. Don't forget linux-next cant't rebased
> because every day a new git tree is created. This is important
> when rebasing commits.
>
> There are also subsystem trees you can pickup to do development.
> Just to name a few:
> - alsa
> - media
> - m68k arch
>
> all have a git tree to work. You can find them on git.kernel.org.
>
If there is a subsystem then should I use the subsystem's tree than
linux-next tree?
> Also:
> - kernel people hate top-posting
> - kernel people hate non-text mail
> - learn git
> - read Documentation/SubmittingPatches **carefully**
> - watch gregkh [1]
>
> http://www.youtube.com/watch?v=LLBrBBImJt4
>
> Good luck,
> Ezequiel.
Thanks for the link.
Thanks,
Sannu
^ permalink raw reply [flat|nested] 4+ messages in thread
* From which tree can I start Linux kernel development
[not found] ` <FB112703C4930F4ABEBB5B763F96491139378F21@MAILSERV2A.lorien.fkie.fgan.de>
@ 2012-06-29 14:41 ` Ezequiel Garcia
0 siblings, 0 replies; 4+ messages in thread
From: Ezequiel Garcia @ 2012-06-29 14:41 UTC (permalink / raw)
To: kernelnewbies
On Fri, Jun 29, 2012 at 9:27 AM, Erdt, Ralph
<ralph.erdt@fkie.fraunhofer.de> wrote:
> Hello,
>
>> There are also subsystem trees you can pickup to do development.
>> Just to name a few:
>> - alsa
>> - media
>> - m68k arch
> Can you please help me?
> Which is the correct subsystem tree for developing a new tc qdisc (dir: net/sched)?
>
Search "net/sched" insied MAINTAINERS file on any linux tree.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-06-29 14:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-28 16:01 From which tree can I start Linux kernel development Sannu K
2012-06-28 21:14 ` Ezequiel Garcia
2012-06-29 14:32 ` Sannu K
[not found] ` <FB112703C4930F4ABEBB5B763F96491139378F21@MAILSERV2A.lorien.fkie.fgan.de>
2012-06-29 14:41 ` Ezequiel Garcia
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.