Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6404] New: Buildroot's coreutils 'uname -p' reports 'Unknown' on recent ARM kernels
Date: Mon, 12 Aug 2013 22:32:46 +0200	[thread overview]
Message-ID: <5209466E.9030305@mind.be> (raw)
In-Reply-To: <bug-6404-163@https.bugs.busybox.net/>

On 01/08/13 06:30, bugzilla at busybox.net wrote:
> Buildroot's coreutils uname(1) command has a special patch applied as part of
> buildroot.  When you run 'uname -p', it tries to print out extended information
> about the processor you are running.  It does this by parsing /proc/cpuinfo.
> I'm not sure of the provenance of this enhancement, but you can read the code
> in package/coreutils/coreutils-uname.patch.

  Seems to me that this patch should be dropped since it's a feature 
patch. Martin, you added it and Gustavo acked it in 2010. OK to drop it?

  Regards,
  Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-08-12 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  4:30 [Buildroot] [Bug 6404] New: Buildroot's coreutils 'uname -p' reports 'Unknown' on recent ARM kernels bugzilla at busybox.net
2013-08-12 20:32 ` Arnout Vandecappelle [this message]
2013-08-13  0:14   ` Martin Banky
2013-08-13  9:20     ` Thomas Petazzoni
2013-08-13 10:12       ` Martin Banky
2013-08-14 12:30   ` Gustavo Zacarias
2013-08-15 13:50     ` Thomas Petazzoni
2013-10-30 22:30 ` [Buildroot] [Bug 6404] " bugzilla at busybox.net

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=5209466E.9030305@mind.be \
    --to=arnout@mind.be \
    --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