From: "Jike Song" <albcamus@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Kbuild: reintroduce ALLSOURCE_ARCHS support for tags/cscope.
Date: Sat, 3 Jan 2009 22:05:49 +0800 [thread overview]
Message-ID: <df9815e70901030605v4e2c2bc2y4827a15fd165d3f4@mail.gmail.com> (raw)
In-Reply-To: <20090102223213.GA8843@uranus.ravnborg.org>
On Sat, Jan 3, 2009 at 6:32 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Wed, Dec 31, 2008 at 09:37:36PM +0800, Jike Song wrote:
>> This patch reintroduce the ALLSOURCE_ARCHS support for tags/TAGS/
>> cscope targets. The Kbuild previously has this feature, but after
>> moving the targets into scripts/tags.sh, ALLSOURCE_ARCHS disappears.
>>
>> It's something like this:
>>
>> $ make ALLSOURCE_ARCHS="x86 mips arm" tags cscope
>
> Hi Jike.
>
> Did you implment this feature because you really use it
> or did you do so because it was 'missing'?
There are many people who works on multiple architectures. As for me,
I work on both x86 and MIPS, and I always specify ALLSOURCE_ARCHS="x86
mips" when building tags/cscope databases. I think this would be a
useful feature for these people;-)
Anyway, it is dependent on your decision.
>
> I explicitly avoided the feature as I expected it to be used
> very seldom.
Maybe just because it is undocumented?
> Sam
>
--
Thanks,
Jike
next prev parent reply other threads:[~2009-01-03 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 13:37 [PATCH] Kbuild: reintroduce ALLSOURCE_ARCHS support for tags/cscope Jike Song
2009-01-02 22:32 ` Sam Ravnborg
2009-01-03 14:05 ` Jike Song [this message]
2009-01-02 22:34 ` Sam Ravnborg
2009-01-03 14:10 ` Jike Song
2009-01-03 20:20 ` Sam Ravnborg
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=df9815e70901030605v4e2c2bc2y4827a15fd165d3f4@mail.gmail.com \
--to=albcamus@gmail.com \
--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