Hi,<div><br><div class="gmail_quote">On Wed, Feb 1, 2012 at 10:51 AM, amit mehta <span dir="ltr"><<a href="mailto:gmate.amit@gmail.com">gmate.amit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br></div><div class="im">
> Also the kernel tree you are using seems to be Linus's mainline, is<br>
> that what you wanted or did you want to be making the patch against a<br>
> linux-next kernel?<br>
<br>
</div>My current goal is to send some patches to kernel janitor group though I'm not<br>
sure if this group is still active or not.<br>
you mean to say that this is not the tree which i should be synced to? If not<br>
then can you please send me the link to the relevant git repository ?<br><font class="Apple-style-span" color="#888888"><br></font></blockquote><div><br></div><div>Please note that linux-next is just a tree used for integration-testing. I strongly suggest</div>
<div>that you don't base your patches on linux-next. Basing it on current mainline</div><div>is generally a good idea. But if you are doing some significant development,</div><div>you should target the individual trees that the subsystem maintainers maintain.</div>
<div><br></div><div>To put it in simple terms, base your patch on current mainline and send it to</div><div>the appropriate people (use <a href="http://get_maintainer.pl">get_maintainer.pl</a> in the scripts directory to find</div>
<div>whom to send it to). Then if the maintainer specifically asks you to rebase your</div><div>patch on some particular tree that he maintains, then do it. Then you know what</div><div>to do with patches related to that subsystem from next time onwards :-)</div>
<div><br></div><div>Some background about linux-next: It is a tree used for integration testing.</div><div>In other words, development trees maintained for different subsystems by the</div><div>respective maintainers will be pulled into the linux-next tree automatically from</div>
<div>time to time. Then the resulting merging of code from different trees are tested</div><div>mainly for build failures (caused due to conflicts etc.). Also, another important</div><div>test carried out is testing the code with various configs, to ensure that it builds</div>
<div>and boots on all relevant config combinations.</div><div><br></div><div>So, to summarize, linux-next is not a development tree. It is only an integration</div><div>testing tree which is used to ensure that during a merge window, when Linus</div>
<div>pulls from different maintainers, the code doesn't end up in conflicts and that</div><div>it builds and boots fine in many different configs.</div><div><br></div><div>Development trees are separate (if any) for different subsystems and that is</div>
<div>usually the best target for heavy code changes. Otherwise, mainline is your</div><div>best bet.</div><div><br></div><div>Hope this helps!</div><div><br></div><div>Regards,</div><div>Srivatsa S. Bhat</div></div></div>