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/1] linux: Don't enable DEVTMPFS support for kernels older than 3.x.
Date: Fri, 18 Apr 2014 21:39:24 +0200	[thread overview]
Message-ID: <20140418213924.6d5a3ebf@skate> (raw)
In-Reply-To: <1397849296-5517-1-git-send-email-rjbarnet@rockwellcollins.com>

Dear Ryan Barnett,

On Fri, 18 Apr 2014 14:28:16 -0500, Ryan Barnett wrote:
> From: Matt Poduska <mjpodusk@rockwellcollins.com>
> 
> In the case where DEVTMPFS is desired for older kernels where the
> support is experimental, it's still possible to enable the option in
> the board's specific linux .config instead of relying on buildroot to
> make the modification.
> 
> Signed-off-by: Matt Poduska <mjpodusk@rockwellcollins.com>
> Signed-off-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
> ---
>  linux/linux.mk |    8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)

Which problem is this fixing? I remember having used devtmpfs prior to
3.x, and it was working well. For versions prior to 2.6.32, the
linux.mk code will set this option that doesn't exist, and the kconfig
code of the kernel will simply get rid of it, without any consequences.

So I'd like to understand the "why" of this patch :)

Thanks!

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

  parent reply	other threads:[~2014-04-18 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 19:28 [Buildroot] [PATCH 1/1] linux: Don't enable DEVTMPFS support for kernels older than 3.x Ryan Barnett
2014-04-18 19:38 ` Peter Korsgaard
2014-04-18 19:39 ` Thomas Petazzoni [this message]
2014-04-22 10:41   ` Luca Ceresoli
2014-04-23 22:45     ` rjbarnet at rockwellcollins.com
2014-04-24  6:49       ` Peter Korsgaard
2014-04-24 19:47         ` Ryan Barnett
2014-04-24 20:00           ` Peter Korsgaard
2014-04-25 13:09             ` Ryan Barnett

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=20140418213924.6d5a3ebf@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