Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] mtd: fix build issues on older hosts
Date: Fri, 7 Jul 2017 11:57:13 +0200	[thread overview]
Message-ID: <20170707115713.3c5d2694@windsurf.lan> (raw)
In-Reply-To: <a942a235-97d6-f1ab-dde6-35525bea8bbf@mind.be>

Hello,

On Fri, 7 Jul 2017 10:21:36 +0200, Arnout Vandecappelle wrote:

> > Patches 1 and 2 applied. Thanks Arnout for the review.  
> 
>  Unfortunately you missed Baruch's comment...

Dammit :-/

And still, I did notice and fixed a mistake that neither you nor Baruch
spotted:

"""
So today, the target variant continues to depend on util-linux, while
the target variant depends on e2fsprogs. 
"""

Obviously the second "target variant" should have been "host variant",
and I fixed that before pushing.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-07-07  9:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 20:58 [Buildroot] [PATCH 1/3] mtd: fix build issues on older hosts Thomas Petazzoni
2017-07-06 20:58 ` [Buildroot] [PATCH 2/3] mtd: host variant needs host-util-linux, host-e2fsprogs Thomas Petazzoni
2017-07-06 22:52   ` Arnout Vandecappelle
2017-07-07  3:23   ` Baruch Siach
2017-07-06 20:58 ` [Buildroot] [PATCH 3/3] mtd: be explicit about config options for the host Thomas Petazzoni
2017-07-06 22:57   ` Arnout Vandecappelle
2017-07-07  8:02     ` Thomas Petazzoni
2017-07-06 22:52 ` [Buildroot] [PATCH 1/3] mtd: fix build issues on older hosts Arnout Vandecappelle
2017-07-07  8:02 ` Thomas Petazzoni
2017-07-07  8:21   ` Arnout Vandecappelle
2017-07-07  9:57     ` 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=20170707115713.3c5d2694@windsurf.lan \
    --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