<br><br><div class="gmail_quote">On Thu, Feb 2, 2012 at 3:35 AM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com">greg@kroah.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">On Thu, Feb 02, 2012 at 02:47:49AM +0530, Srivatsa Bhat wrote:<br>
> Hi,<br>
><br>
> On Wed, Feb 1, 2012 at 10:51 AM, amit mehta <<a href="mailto:gmate.amit@gmail.com">gmate.amit@gmail.com</a>> wrote:<br>
><br>
><br>
> > 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>
> My current goal is to send some patches to kernel janitor group though I'm<br>
> 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<br>
> not<br>
> then can you please send me the link to the relevant git repository ?<br>
><br>
><br>
><br>
> Please note that linux-next is just a tree used for integration-testing. I<br>
> strongly suggest<br>
> that you don't base your patches on linux-next. Basing it on current mainline<br>
> is generally a good idea. But if you are doing some significant development,<br>
> you should target the individual trees that the subsystem maintainers maintain.<br>
><br>
> To put it in simple terms, base your patch on current mainline and send it to<br>
> the appropriate people (use <a href="http://get_maintainer.pl" target="_blank">get_maintainer.pl</a> in the scripts directory to find<br>
> whom to send it to). Then if the maintainer specifically asks you to rebase<br>
> your<br>
> patch on some particular tree that he maintains, then do it. Then you know what<br>
> to do with patches related to that subsystem from next time onwards :-)<br>
<br>
</div>As a subsystem maintainer, I strongly disagree with this.<br>
<br>
Do your work against linux-next, as that contains the different<br>
subsystems already. You don't want to do something only to find out you<br>
need to totally redo it, or just throw it away as someone else has<br>
already done it (which is quite common for janitorial and other "simple"<br>
tasks).<br>
<br></blockquote><div><br></div><div>Ok, that makes sense.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So please, either work against linux-next, or the subsystem-specific<br>
tree, linux-next is usually easier, the odds of cross-subsystem merges<br>
causing problems with your change, for the subsystem maintainer, are<br>
very low, much lower than the fact that major changes might have already<br>
happened.<br></blockquote><div><br></div><div>I see your point, and I agree with you now.</div><div>Thanks a lot Greg, for showing the right path!</div><div><br></div><div>Regards,</div><div>Srivatsa S. Bhat</div></div>