From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] cris kernel headers
Date: Mon, 23 Jun 2008 15:11:12 +0200 [thread overview]
Message-ID: <20080623131112.GD8920@mx.loc> (raw)
In-Reply-To: <485F76F9.5030705@cetrtapot.si>
On Mon, Jun 23, 2008 at 12:12:09PM +0200, Hinko Kocevar wrote:
>Hi,
>
>GIT commit http://repo.or.cz/w/buildroot.git?;a=commit;h=6217a8ab0daee6cac61c2372d9b9deb9dd9c802c does not solve the missing headers problem for cris (at least not for me).
>
>I'll ask on dev-etrax list if anyone there could shed some light on the subject.
Yes, that's expected, see the other mail i just sent. Shouldn't be hard
to fix.
prev parent reply other threads:[~2008-06-23 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 10:12 [Buildroot] cris kernel headers Hinko Kocevar
2008-06-23 13:11 ` Bernhard Fischer [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=20080623131112.GD8920@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.