Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] DirectFB + linux-headers-2.6.28.1 compilation problem
Date: Fri, 23 Jan 2009 14:14:51 +0100	[thread overview]
Message-ID: <87d4eekvuc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <fce2a370901230456m52a0b2d4xd74c5121ec3cdd6d@mail.gmail.com> (Ihar Hrachyshka's message of "Fri\, 23 Jan 2009 14\:56\:40 +0200")

>>>>> "Ihar" == Ihar Hrachyshka <ihar.hrachyshka@gmail.com> writes:

Hi,

 >> Yes. Seems to be a problem in the kernel headers.

 Ihar> Yes, it's a kernel headers bug. Should be fixed for next versions I think.

Could you retry with r24981?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-01-23 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 11:10 [Buildroot] DirectFB + linux-headers-2.6.28.1 compilation problem Ihar Hrachyshka
2009-01-23 11:18 ` Sven Neumann
2009-01-23 12:49 ` Peter Korsgaard
2009-01-23 12:54   ` Sven Neumann
2009-01-23 12:56     ` Ihar Hrachyshka
2009-01-23 13:05       ` Peter Korsgaard
2009-01-23 13:14       ` Peter Korsgaard [this message]
2009-01-23 12:58     ` Peter Korsgaard
2009-01-23 13:00       ` Ihar Hrachyshka

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=87d4eekvuc.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox