From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] util-linux: nommu: Add patch to use vfork in nommu arch.
Date: Thu, 14 Nov 2013 00:23:14 +0100 [thread overview]
Message-ID: <20131114002314.72c4b4a1@skate> (raw)
In-Reply-To: <52840758.10104@mind.be>
Arnout, Sonic,
On Thu, 14 Nov 2013 00:12:24 +0100, Arnout Vandecappelle wrote:
> > +diff -urN util-linux-2.23.2.old/fdisks/fdiskbsdlabel.h util-linux-2.23.2/fdisks/fdiskbsdlabel.h
> > +--- util-linux-2.23.2.old/fdisks/fdiskbsdlabel.h 2013-07-30 16:54:15.362994206 +0800
> > ++++ util-linux-2.23.2/fdisks/fdiskbsdlabel.h 2013-11-11 14:52:18.285623027 +0800
> > +@@ -50,7 +50,7 @@
> > + defined (__mips__) || defined (__s390__) || defined (__sh__) || \
> > + defined (__aarch64__) || defined(__xtensa__) || \
> > + defined (__x86_64__) || defined (__avr32__) || defined(__cris__) || \
> > +- defined (__microblaze__)
> > ++ defined(__bfin__) || defined (__microblaze__)
>
> This is actually a blackfin change, not a nommu change, so it should be
> a separate patch.
Just a quick note to mention that util-linux 2.24 has removed this
header, and we have a patch pending to bump util-linux to 2.24. See
http://patchwork.ozlabs.org/patch/290366/.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-13 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 10:29 [Buildroot] [PATCH 1/2] util-linux: nommu: Add patch to use vfork in nommu arch sonic.adi at gmail.com
2013-11-11 10:29 ` [Buildroot] [PATCH 2/2] util-linux: flat: Add patch to avoid creating dynamic libraries sonic.adi at gmail.com
2013-11-13 23:12 ` [Buildroot] [PATCH 1/2] util-linux: nommu: Add patch to use vfork in nommu arch Arnout Vandecappelle
2013-11-13 23:23 ` Thomas Petazzoni [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=20131114002314.72c4b4a1@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox