Kconfig recursion error

[Amit Kumar]

On Wed, Nov 23, 2016 at 12:27 PM Greg KH <greg at kroah.com> wrote:

> On Wed, Nov 23, 2016 at 04:36:57AM +0000, Amit Kumar wrote:
> >
> >
> > On Tue, Nov 22, 2016 at 10:32 PM Blatinox <blatinox at lse.epita.fr> wrote:
> >
> >     Hi Amit,
> >
> >     On Tue, 22 Nov 2016 11:30:06 +0000
> >     Amit Kumar <free.amit.kumar at gmail.com> wrote:
> >
> >     > On Tue, Nov 22, 2016 at 4:51 PM Amit Kumar <
> free.amit.kumar at gmail.com>
> >     > wrote:
> >     >
> >     > > Hi,
> >     > > When I configure  kernel like,
> >     > > CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm make
> omap2plus_defconfig
> >     > > I get error as follows,
> >     > > HOSTCC  scripts/basic/fixdep
> >     > >   HOSTCC  scripts/kconfig/conf.o
> >     > >   SHIPPED scripts/kconfig/zconf.tab.c
> >     > >   SHIPPED scripts/kconfig/zconf.lex.c
> >     > >   SHIPPED scripts/kconfig/zconf.hash.c
> >     > >   HOSTCC  scripts/kconfig/zconf.tab.o
> >     > >   HOSTLD  scripts/kconfig/conf
> >     > > drivers/remoteproc/Kconfig:3:error: recursive dependency
> detected!
> >     > > For a resolution refer to
> Documentation/kbuild/kconfig-language.txt
> >     > > subsection "Kconfig recursive dependency limitations"
> >     > > drivers/remoteproc/Kconfig:3: symbol REMOTEPROC is selected by
> >     > > QCOM_ADSP_PIL
> >     > > For a resolution refer to
> Documentation/kbuild/kconfig-language.txt
> >     > > subsection "Kconfig recursive dependency limitations"
> >     > > drivers/remoteproc/Kconfig:81: symbol QCOM_ADSP_PIL depends on
> >     REMOTEPROC
> >     > > #
> >     > > # configuration written to .config
> >     > > #
> >     > > I think Documentation/kbuild/Kconfig.recursion-issue-02 is
> applicable,
> >     > > because REMOTEPROC is mentioned in depends on and select at
> different
> >     > > places.
> >     > >
> >     > > I am using a branch based on next-20161117.
> >     >
> >     It has been fixed by commit cc7d54b05057 ("remoteproc: adsp-pil: fix
> >     recursive dependency") available since next-20161122.
> >
> >     I am wondering one thing: is the dependency on REMOTEPROC necessary
> >     for QCOM_ADSP_PIL symbol (and other symbols in the same file) even if
> >     this symbol is defined inside an 'if REMOTEPROC' block ?
> >
> >
> > Yes it works in next-20161122. I'm in IST so I get next tree update the
> next
> > day. If I want to create a linux-next tree and publish it on github
> publicly
> > then what I need to do?
>
> Why do you want to push this to github?  What is that going to help out
> with?
>
> I want to create my own linux-next tree and update it before every patch
creation. I think update of maintainers repos should be available as
quickly as possible to the community so that duplicate patch submission and
report of bug which has been already debugged as in this thread can be
avoided. When I reported this bug, It was debugged already but linux-next
tree was not up-to-date.

I want to make it public so that other community members may be benefited.


> > I think MAINTAINERS file may provide maintainers repos but there may be
> certain
> > tasks to be performed which I as a newbie don't know.
>
> I don't understand this statement.
>
 I think repos to assemble my linux-next tree can be found in the
MAINTAINERS file.

>
> > I also want to do this because as push, pulling don't require
> authentication.
>
> What does this mean?
>
I'm not a privileged member of the Linux community so I've no push
authentication. But pulling of a repo, as I think, does not require any
authentication.

What I need to do to assemble my linux-next tree?
I request you to provide me your guidance.


> Have you gone through the "how to write your first kernel patch"
> tutorial on kernelnewbies.org?  That should help answer these types of
> questions.
> I'm able to create a patch and send it using git-send-email. Download it
> using mutt and apply it using git-am.

 http://www.freeark1.info/2016/11/contents.html
ASAP I'm going to write more kernel articles.
Regards,
Amit Kumar

>
> thanks,
>
> greg k-h
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161123/27036ede/attachment.html