From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10171] devmem2 w (word) is 8 bytes in x86 64 systems
Date: Mon, 12 Aug 2019 20:40:51 +0000 [thread overview]
Message-ID: <bug-10171-163-8GfxQGSeqA@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10171-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10171
--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks Carlos for taking care of the issue. It certainly makes sense to use the
devmem applet from Busybox, when Busybox is enabled.
However, I'm wondering if it makes sense to keep a standalone version of this
program. Most (all?) applets provided by Busybox also have a counterpart
"full-blown" version, which can be useful in situations where Busybox is not
used.
Overall, it feels like this bug is not really a Buildroot bug: it's an upstream
devmem2 bug, which should be reported to upstream and not to Buildroot.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-12 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 20:20 [Buildroot] [Bug 10171] New: devmem2 w (word) is 8 bytes in x86 64 systems bugzilla at busybox.net
2017-08-07 13:53 ` [Buildroot] [Bug 10171] " bugzilla at busybox.net
2017-08-07 16:00 ` bugzilla at busybox.net
2019-08-11 0:34 ` bugzilla at busybox.net
2019-08-11 6:23 ` bugzilla at busybox.net
2019-08-11 23:16 ` bugzilla at busybox.net
2019-08-12 20:40 ` bugzilla at busybox.net [this message]
2019-08-12 23:28 ` bugzilla at busybox.net
2019-09-23 20:10 ` 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=bug-10171-163-8GfxQGSeqA@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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