From: Sam Ravnborg <sam@ravnborg.org>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, dwmw2@infradead.org,
linux-next@vger.kernel.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Thu, 12 Mar 2009 21:58:26 +0100 [thread overview]
Message-ID: <20090312205826.GA14205@uranus.ravnborg.org> (raw)
In-Reply-To: <200903121503.37195.rob@landley.net>
> > And if you look up the content of "include/asm-generic/Kbuild.asm"
>
> Ah, I was grepping for header-y and this is full of unifdef-y, so I didn't
> look too closely at this file. (I did glance at it, but the first thing I saw
> was "errno.h" and there's an errno.h in the include/asm-generic directory, so
> I thought it was describing itself. I presume it tries the arch one first and
> falls back to asm-generic if it's not there?)
No - it uses what it is told to use. Look again.
We have in asm-generic two files:
Kbuild <= what is exported always and located in asm-generic
Kbuild.asm <= exported from archs asm - just a common list of file names
>
>
> Seems kind of silly to let git grind away downloading hundreds of megabytes of
> history that'll just get wiped (especially since that tree gets regenerated
> nightly), but oh well. Assuming that kernel development is git-centric enough
> that a tarball version of a regenerated nightly resource just never seemed
> important, said git repository would be on git.kernel.org, but where...
> linux/kernel/git/eranian/linux-next.git isn't it...
> linux/kernel/git/mchehab/linux-next.git isn't it...
> Ah, linux/kernel/git/sfr/linux-next.git is the one I'm looking for. Now where
> was the magic incantation to translate from the web url to a git url... Ah,
> at the top of the page.
Usual people read the announcement mails from Stephen and follow the instructions there.
And many people keep an updated git tree around speeding up the process.
I cannot remember when I clone a full kernel tree - long time ago for sure.
Sam
next prev parent reply other threads:[~2009-03-12 20:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 9:37 Rob Landley
2009-03-12 9:58 ` Sam Ravnborg
2009-03-12 20:03 ` Rob Landley
2009-03-12 20:58 ` Sam Ravnborg [this message]
2009-03-12 23:24 ` Stephen Rothwell
2009-03-12 21:02 ` Sam Ravnborg
2009-03-12 22:40 ` Geert Uytterhoeven
2009-03-13 3:25 ` Rob Landley
2009-03-13 7:04 ` Greg Ungerer
2009-03-13 8:25 ` Sam Ravnborg
2009-03-13 8:33 ` Geert Uytterhoeven
2009-03-13 8:59 ` Sam Ravnborg
2009-03-13 10:52 ` Greg Ungerer
2009-03-13 12:14 ` Geert Uytterhoeven
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 20:20 ` Rob Landley
2009-03-16 22:08 ` Geert Uytterhoeven
2009-03-16 23:09 ` Greg Ungerer
2009-03-16 23:10 ` Greg Ungerer
2009-03-18 4:03 ` Rob Landley
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 18:12 ` Rob Landley
2009-03-18 23:53 ` Greg Ungerer
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 8:41 ` Rob Landley
2009-03-13 8:25 ` Geert Uytterhoeven
2009-03-13 6:53 ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03 ` Sam Ravnborg
2009-04-01 19:48 ` Lennart Sorensen
2009-04-01 20:23 ` Geert Uytterhoeven
2009-04-01 22:59 ` Lennart Sorensen
2009-04-02 2:14 ` Rob Landley
2009-04-02 21:59 ` Lennart Sorensen
2009-04-03 0:24 ` Rob Landley
2009-04-03 4:10 ` Lennart Sorensen
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=20090312205826.GA14205@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rob@landley.net \
/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
Powered by JetHome