<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Nov 23, 2016 at 2:21 PM Greg KH <<a href="mailto:greg@kroah.com">greg@kroah.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Nov 23, 2016 at 07:54:48AM +0000, Amit Kumar wrote:<br class="gmail_msg">
> On Wed, Nov 23, 2016 at 12:27 PM Greg KH <<a href="mailto:greg@kroah.com" class="gmail_msg" target="_blank">greg@kroah.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> > On Wed, Nov 23, 2016 at 04:36:57AM +0000, Amit Kumar wrote:<br class="gmail_msg">
> > ><br class="gmail_msg">
> > ><br class="gmail_msg">
> > > On Tue, Nov 22, 2016 at 10:32 PM Blatinox <<a href="mailto:blatinox@lse.epita.fr" class="gmail_msg" target="_blank">blatinox@lse.epita.fr</a>> wrote:<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > Hi Amit,<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > On Tue, 22 Nov 2016 11:30:06 +0000<br class="gmail_msg">
> > > Amit Kumar <<a href="mailto:free.amit.kumar@gmail.com" class="gmail_msg" target="_blank">free.amit.kumar@gmail.com</a>> wrote:<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > > On Tue, Nov 22, 2016 at 4:51 PM Amit Kumar <<br class="gmail_msg">
> > <a href="mailto:free.amit.kumar@gmail.com" class="gmail_msg" target="_blank">free.amit.kumar@gmail.com</a>><br class="gmail_msg">
> > > > wrote:<br class="gmail_msg">
> > > ><br class="gmail_msg">
> > > > > Hi,<br class="gmail_msg">
> > > > > When I configure kernel like,<br class="gmail_msg">
> > > > > CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm make<br class="gmail_msg">
> > omap2plus_defconfig<br class="gmail_msg">
> > > > > I get error as follows,<br class="gmail_msg">
> > > > > HOSTCC scripts/basic/fixdep<br class="gmail_msg">
> > > > > HOSTCC scripts/kconfig/conf.o<br class="gmail_msg">
> > > > > SHIPPED scripts/kconfig/zconf.tab.c<br class="gmail_msg">
> > > > > SHIPPED scripts/kconfig/zconf.lex.c<br class="gmail_msg">
> > > > > SHIPPED scripts/kconfig/zconf.hash.c<br class="gmail_msg">
> > > > > HOSTCC scripts/kconfig/zconf.tab.o<br class="gmail_msg">
> > > > > HOSTLD scripts/kconfig/conf<br class="gmail_msg">
> > > > > drivers/remoteproc/Kconfig:3:error: recursive dependency<br class="gmail_msg">
> > detected!<br class="gmail_msg">
> > > > > For a resolution refer to<br class="gmail_msg">
> > Documentation/kbuild/kconfig-language.txt<br class="gmail_msg">
> > > > > subsection "Kconfig recursive dependency limitations"<br class="gmail_msg">
> > > > > drivers/remoteproc/Kconfig:3: symbol REMOTEPROC is selected by<br class="gmail_msg">
> > > > > QCOM_ADSP_PIL<br class="gmail_msg">
> > > > > For a resolution refer to<br class="gmail_msg">
> > Documentation/kbuild/kconfig-language.txt<br class="gmail_msg">
> > > > > subsection "Kconfig recursive dependency limitations"<br class="gmail_msg">
> > > > > drivers/remoteproc/Kconfig:81: symbol QCOM_ADSP_PIL depends on<br class="gmail_msg">
> > > REMOTEPROC<br class="gmail_msg">
> > > > > #<br class="gmail_msg">
> > > > > # configuration written to .config<br class="gmail_msg">
> > > > > #<br class="gmail_msg">
> > > > > I think Documentation/kbuild/Kconfig.recursion-issue-02 is<br class="gmail_msg">
> > applicable,<br class="gmail_msg">
> > > > > because REMOTEPROC is mentioned in depends on and select at<br class="gmail_msg">
> > different<br class="gmail_msg">
> > > > > places.<br class="gmail_msg">
> > > > ><br class="gmail_msg">
> > > > > I am using a branch based on next-20161117.<br class="gmail_msg">
> > > ><br class="gmail_msg">
> > > It has been fixed by commit cc7d54b05057 ("remoteproc: adsp-pil: fix<br class="gmail_msg">
> > > recursive dependency") available since next-20161122.<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > I am wondering one thing: is the dependency on REMOTEPROC necessary<br class="gmail_msg">
> > > for QCOM_ADSP_PIL symbol (and other symbols in the same file) even if<br class="gmail_msg">
> > > this symbol is defined inside an 'if REMOTEPROC' block ?<br class="gmail_msg">
> > ><br class="gmail_msg">
> > ><br class="gmail_msg">
> > > Yes it works in next-20161122. I'm in IST so I get next tree update the<br class="gmail_msg">
> > next<br class="gmail_msg">
> > > day. If I want to create a linux-next tree and publish it on github<br class="gmail_msg">
> > publicly<br class="gmail_msg">
> > > then what I need to do?<br class="gmail_msg">
> ><br class="gmail_msg">
> > Why do you want to push this to github? What is that going to help out<br class="gmail_msg">
> > with?<br class="gmail_msg">
> ><br class="gmail_msg">
> I want to create my own linux-next tree and update it before every patch<br class="gmail_msg">
> creation. I think update of maintainers repos should be available as<br class="gmail_msg">
> quickly as possible to the community so that duplicate patch submission and<br class="gmail_msg">
> report of bug which has been already debugged as in this thread can be<br class="gmail_msg">
> avoided. When I reported this bug, It was debugged already but linux-next<br class="gmail_msg">
> tree was not up-to-date.<br class="gmail_msg">
<br class="gmail_msg">
No tree can ever be as up-to-date as possible given the huge numbers of<br class="gmail_msg">
patches being sent in for different issues. The best that you can do is<br class="gmail_msg">
to subscribe to a specific mailing list for a subsystem that you care<br class="gmail_msg">
about and follow along with development through email there.<br class="gmail_msg">
<br class="gmail_msg">
> I want to make it public so that other community members may be benefited.<br class="gmail_msg">
<br class="gmail_msg">
How exactly?<br class="gmail_msg">
<br class="gmail_msg">
And realize that linux-next is a huge tree that gets rebuilt every<br class="gmail_msg">
week-day. Pushing that out to github is a huge waste of bandwidth and<br class="gmail_msg">
storage for very little gain.<br class="gmail_msg">
<br class="gmail_msg">
> > > I think MAINTAINERS file may provide maintainers repos but there may be<br class="gmail_msg">
> > certain<br class="gmail_msg">
> > > tasks to be performed which I as a newbie don't know.<br class="gmail_msg">
> ><br class="gmail_msg">
> > I don't understand this statement.<br class="gmail_msg">
> ><br class="gmail_msg">
> I think repos to assemble my linux-next tree can be found in the<br class="gmail_msg">
> MAINTAINERS file.<br class="gmail_msg">
<br class="gmail_msg">
If you wish to duplicate linux-next on your own, look at the list of<br class="gmail_msg">
trees that linux-next pulls in. It's in the tree itself as part of its<br class="gmail_msg">
own documentation. It's not just trees found in the MAINTAINERS file.<br class="gmail_msg">
Yes, we can find list of trees in "git show".<br class="gmail_msg"></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> > > I also want to do this because as push, pulling don't require<br class="gmail_msg">
> > authentication.<br class="gmail_msg">
> ><br class="gmail_msg">
> > What does this mean?<br class="gmail_msg">
> ><br class="gmail_msg">
> I'm not a privileged member of the Linux community so I've no push<br class="gmail_msg">
> authentication. But pulling of a repo, as I think, does not require any<br class="gmail_msg">
> authentication.<br class="gmail_msg">
<br class="gmail_msg">
No one in the kernel community has "push authentication", we all just<br class="gmail_msg">
have our own trees that some happen to send pull requests to Linus at<br class="gmail_msg">
some time.<br class="gmail_msg">
<br class="gmail_msg">
See how we all work by reading Documentation/development_process/<br class="gmail_msg">
That should help answer some of your questions.<br class="gmail_msg">
In next-20161122, There is Documentation/process/ which contains rst files. I'm going to read it thoroughly. <br class="gmail_msg">
> What I need to do to assemble my linux-next tree?<br class="gmail_msg">
<br class="gmail_msg">
See above, but I really don't think that it's something you want to do<br class="gmail_msg">
if you don't have a lot of experience with git and merges and kernel<br class="gmail_msg">
development, as it is a _very_ complex thing.<br class="gmail_msg">
<br class="gmail_msg"></blockquote><div>Time makes anything easy and time turns a hobby into job.</div><div>Regards,</div><div>Amit Kumar </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Good luck!<br class="gmail_msg">
<br class="gmail_msg">
greg k-h<br class="gmail_msg">
</blockquote></div></div>