public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: KBUILD: do not include arch/<ARCH>/include/asm in find-sources twice.
Date: Wed, 29 Oct 2008 19:51:13 +0000	[thread overview]
Message-ID: <1225309873.5267.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20081029190707.GD22105@uranus.ravnborg.org>

On Wed, 2008-10-29 at 20:07 +0100, Sam Ravnborg wrote:
> On Tue, Oct 28, 2008 at 01:36:25PM +0000, Ian Campbell wrote:
> > Architectures which have moved their includes to arch/<ARCH>/include
> > now list the headers twice in the source listing used by "make
> > cscope" and friends, causing those tools to list symbols twice.
> > 
> > Skipping these files in the ALLSOURCE_ARCHS pass rather than removing
> > the ALLINCLUDE_ARCHS pass preserves the semantics of the later.
> > 
> > Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
> > Cc: Sam Ravnborg <sam@ravnborg.org>
> > Cc: linux-kbuild@vger.kernel.org
> > 
> > diff -r a613b893f5b5 Makefile
> > --- a/Makefile	Mon Oct 27 10:29:49 2008 +0000
> > +++ b/Makefile	Tue Oct 28 13:33:04 2008 +0000
> > @@ -1435,7 +1435,8 @@
> >  define find-sources
> >          ( for arch in $(ALLSOURCE_ARCHS) ; do \
> >  	       find $(__srctree)arch/$${arch} $(RCS_FIND_IGNORE) \
> > -	            -name $1 -print; \
> > +		    -wholename $(__srctree)arch/$${arch}/include/asm -type d -prune \
> > +	            -o -name $1 -print; \
> >  	  done ; \
> >  	  find $(__srctree)security/selinux/include $(RCS_FIND_IGNORE) \
> >  	       -name $1 -print; \
> > 
> 
> Hi Ian.
> 
> I would much rather prefer to see a patch that
> - support the platforms of arm and others

How do you mean?

        $ ls arch/arm/include/
        asm/

so it'll work as well for arm as it does for any other architecture.

All this patch does is stop the ALLSOURCE_ARCH loop from covering files
which are also picked up by the ALLINCLUDE_ARCH loop. Including those
files twice is a regression from before the headers got moved.

> - uses the fact that all arch have their header files moved
>   to arch/$ARCH/include
>   [Ignore the archs that are lacking behind]

in that case you would simply also remove the :
		test -e $(__srctree)include/asm-$${arch} && \
                 find $(__srctree)include/asm-$${arch} $(RCS_FIND_IGNORE) \
                    -name $1 -print; \
from the ALLINCLUDE_ARCHS loop.

> And if we could simplify this "find file" list on top of that it would be extra bonus.

Unless you want to get rid of the distinction between ALLINCLUDE_ARCHS
and ALLSOURCE_ARCHS I don't think it can get any simpler. If you did
want to get rid of that distinction then it would simply be a case of
removing the ALLINCLUDE_ARCHS loop and ignoring this patch.

Ian.
-- 
Ian Campbell

Perhaps they will have to outlaw sending random lists of words.  fee fie
foe foo [sic]
		-- Larry Wall in <199710311916.LAA19760@wall.org>


  reply	other threads:[~2008-10-29 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 13:36 KBUILD: do not include arch/<ARCH>/include/asm in find-sources twice Ian Campbell
2008-10-29 19:07 ` Sam Ravnborg
2008-10-29 19:51   ` Ian Campbell [this message]
2008-10-29 21:29     ` Sam Ravnborg
2008-10-30 11:02   ` Ian Campbell
2008-10-30 11:09     ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1225309873.5267.10.camel@localhost.localdomain \
    --to=ijc@hellion.org.uk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox