Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] glibc 2.7 and 2.9 (arm): Remove unnecessary asm/page.h include
Date: Mon, 17 Aug 2009 16:01:10 +0100	[thread overview]
Message-ID: <1250521270.27980.6.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200908171606.57153.holger+oe@freyther.de>

On Mon, 2009-08-17 at 16:06 +0200, Holger Hans Peter Freyther wrote:
> To be honest I wonder why you are triggering this area, and why other builds 
> don't do that... it is  a bit frightening.

I expect it's nothing more sinister than different versions of
linux-libc-headers.  <asm/page.h> was there in 2.6.23 but, it seems,
gone by 2.6.29.  So, probably no cause for alarm.

p.





  reply	other threads:[~2009-08-17 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 13:53 [PATCH] glibc 2.7 and 2.9 (arm): Remove unnecessary asm/page.h include Jonathan Cameron
2009-08-17 14:06 ` Holger Hans Peter Freyther
2009-08-17 15:01   ` Phil Blundell [this message]
2009-08-17 15:02     ` Phil Blundell
2009-08-18  9:06       ` Otavio Salvador
2009-08-19 11:06         ` Jonathan Cameron
2009-08-18 13:26   ` Jonathan Cameron

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=1250521270.27980.6.camel@mill.internal.reciva.com \
    --to=pb@reciva.com \
    --cc=openembedded-devel@lists.openembedded.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