From: Sam Ravnborg <sam@ravnborg.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-am33-list@redhat.com
Subject: Re: [PATCH 0/6] MN10300: Add the MN10300 architecture to Linux kernel [try #4]
Date: Thu, 8 Nov 2007 23:04:55 +0100 [thread overview]
Message-ID: <20071108220455.GB28242@uranus.ravnborg.org> (raw)
In-Reply-To: <16966.1194549065@redhat.com>
Hi David.
> > arch/mn10300/Makefile:
> >
> > 1) Use KBUILD_CFLAGS & KBUILD_AFLAGS & KBUILD_CPPFLAGS - they
> > have replaced the former xFLAGS.
>
> Done. What about ASFLAGS and LDFLAGS?
kbuild does not know anything about ASFLAGS.
In the whole kernel tree I only see frv assign them but the
value is never used.
LDFLAGS has not been changed - it was not such an easy cut.
And we anyway use the linker in much more ways so when to
use it and when not...
> > 4) Drop the symlinks - they are evil...
> > Use a structure like:
> > include/asm-mn10300/asb2303/proc/*.h
>
> No. I think all the arch headers should really appear to be #included under
> asm/. That means that the structure would have to be:
>
> include/asm-mn10300/asb2303/asm/proc/*.h
>
> That then puts all these header files several levels further down, which isn't
> that good.
I would prefer that any day as replacement for the symlinks.
But as everyone else seems so happy with the symlinks do whatever you prefer.
> > Then you adjust -I include/asm-mn10300/asb2303
> > and no symlinks needed.
> > And if you change processor kbuild will notice
> > and recompile everything.
>
> That's the only plus, but it's a smaller plus than not interpolating several
> levels of almost empty directory into the paths for the proc- and unit-specific
> headers.
>
> > No-one else does it this way but mn10300 could show how to do it.
>
> I could. Or I could do what everyone else does.
>
> Actually, what you perhaps ought to do for a start is to move the individual
> include/asm-$ARCH dirs to arch/$ARCH/asm and then you can avoid that symlink
> too.
It will wait until we save ARCH so we can detect
ARCH changes.
>
> > 5)
> > +zImage: vmlinux
> > + $(Q)$(MAKE) $(build)=$(boot) $(KBUILD_IMAGE)
> > +
> > +all: zImage
> > +
> > +Image: vmlinux
> > + $(Q)$(MAKE) $(build)=arch/mn10300/boot $@
> >
> > This could be done as:
> > +Image zImage: vmlinux
> > + $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
>
> Done.
>
> > And then modify boot/Makefile accordingly
>
> I don't see why it needs modification. $(KBUILD_IMAGE) == $(boot)/zImage for
> the zImage target.
For the Image target it is Image without $(boot)/ but that target
was never supported anyway.
> > 1) You can safely remove the copyright of Linus..
> > Same goes for other places where his copyright are kept but filecontent
> > is new.
>
> The copyright assignment on some of these files was made by MEI. I'm not sure
> I can change them.
It just seemed stupid that someone having copyright on a file
where the person only had contributed the copyright linei (for said file).
Sam
next prev parent reply other threads:[~2007-11-08 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071108171637.26590.27076.stgit@warthog.procyon.org.uk>
2007-11-08 17:16 ` David Howells
2007-11-08 17:16 ` [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT " David Howells
2007-11-08 17:16 ` [PATCH 2/6] MTD: Add support for the SST 39VF1601 flash chip " David Howells
2007-11-08 17:16 ` [PATCH 3/6] USB: net2280 can't have a function called show_registers() " David Howells
2007-11-08 17:16 ` [PATCH 4/6] MN10300: Allocate serial port UART IDs for on-chip serial ports " David Howells
2007-11-08 17:16 ` [PATCH 6/6] MN10300: Add MTD flash support for the ASB2303 board " David Howells
2007-11-08 18:15 ` [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel " David Howells
2007-11-08 18:29 ` [PATCH 0/6] MN10300: Add the MN10300 architecture to Linux " Sam Ravnborg
2007-11-08 19:11 ` David Howells
2007-11-08 22:04 ` Sam Ravnborg [this message]
2007-11-08 23:30 ` David Howells
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=20071108220455.GB28242@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®