From: Sam Ravnborg <sam@ravnborg.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>,
Michal Marek <mmarek@suse.cz>,
linux-media@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [RFC PATCH] media: consolidation of -I flags
Date: Wed, 06 Oct 2010 04:52:55 +0000 [thread overview]
Message-ID: <20101006045255.GA24870@merkur.ravnborg.org> (raw)
In-Reply-To: <20101005192435.GA17798@haskell.muteddisk.com>
>
> Ah, I was not aware of that, and I forgot to test for that case.
>
> > >
> > > If neither idea is considered beneficial, I will go ahead and replace
> > > the older variables with the newer ones as is.
> >
> > This is the right approach.
> >
> > You could consider to do a more general cleanup:
> > 1) replace EXTRA_CFLAGS with ccflags-y (the one you suggest)
> > 2) replace use of <module>-objs with <module>-y
> > 3) break continued lines into several assignments
> > People very often uses '\' to break long lines, where a
> > simple += would be much more readable.
> > But this topic may be personal - I never uses "\" in my .c code unless in macros,
> > and I have applied the same rule for Makefiles.
> > An ugly example is drivers/media/Makefile
> > 4) In general use ":=" instead of "=".
> > Add using "+=" as first assignment is OK - but it just looks plain wrong
> > 5) some files has a mixture of spaces/tabs (are red in my vim)
> > dvb-core/Makefile is one such example
> > 6) remove useless stuff
> > siano/Makefile has some strange assignments to EXTRA_CFLAGS
> > 7) Likely a few more items to look after...
> >
> > This is more work - but then you finish a Makefile rather than doing a simple
> > conversion.
>
> I agree with all your points above; however, I was unsure of whether a wholesale
> cleanup would be welcomed because I would then end up touching numerous lines
> (and in some cases, possibly all lines).
The Makefiles are all very simple - so touching all lines in a files
is not a big deal here. But then you would have to batch your changes
in smaller parts touching only a few Makefiles/one Makefile per patch.
> Is the use of <module>-objs deprecated? Some people might wonder why I am
> changing that when they are not building a multisource object.
I always recommends the <module>-y notation.
Because this version has the flexibility to use the kbuild way
of dealing with conditional modules.
I see no reason to do such change alaone - but as part of other minor
cleanups it would be natural to change to the <module>-y idiom.
All the comments above is valid for staging too. There we should
try to do general cleanup on the Makefile rather than a lot of small
edits.
But sometimes the MAkefiles contains so much legacy that this will be more
than one patch..
Sam
prev parent reply other threads:[~2010-10-06 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 21:00 [RFC PATCH] media: consolidation of -I flags matt mooney
2010-10-05 14:29 ` Sam Ravnborg
2010-10-05 19:24 ` matt mooney
2010-10-05 22:27 ` T Dent
2010-10-05 23:53 ` matt mooney
2010-10-06 0:52 ` T Dent
2010-10-05 23:44 ` matt mooney
2010-10-06 4:52 ` Sam Ravnborg [this message]
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=20101006045255.GA24870@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mmarek@suse.cz \
/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