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 v2 1/3] inadyn: do not install default conf file
Date: Mon, 17 Oct 2016 17:41:39 +0200	[thread overview]
Message-ID: <20161017174139.260ee7be@free-electrons.com> (raw)
In-Reply-To: <20161017142524.12026-1-bluemrp9@gmail.com>

Hello,

On Mon, 17 Oct 2016 07:25:22 -0700, Ryan Coe wrote:

> The default conf file is not usable without modification.

Right, but it provide a good starting point.

> It is also not compatible with the newer 2.0 series.

This is not really an excuse, it should simply be updated together with
the bump to 2.0.

Thanks,

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

      parent reply	other threads:[~2016-10-17 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 14:25 [Buildroot] [PATCH v2 1/3] inadyn: do not install default conf file Ryan Coe
2016-10-17 14:25 ` [Buildroot] [PATCH v2 2/3] inadyn: bump to version 2.0 Ryan Coe
2016-10-17 14:25 ` [Buildroot] [PATCH v2 3/3] DEVELOPERS: add entry for inadyn Ryan Coe
2016-10-17 15:41 ` 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=20161017174139.260ee7be@free-electrons.com \
    --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