Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752310AbdHHLqc (ORCPT <rfc822;w@1wt.eu>);
        Tue, 8 Aug 2017 07:46:32 -0400
Received: from www17.your-server.de ([213.133.104.17]:32992 "EHLO
        www17.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751925AbdHHLqa (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 8 Aug 2017 07:46:30 -0400
Date: Tue, 8 Aug 2017 13:46:25 +0200
From: Thomas Meyer <thomas@m3y3r.de>
To: rob@landley.net
Cc: linux-kernel@vger.kernel.org
Subject: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?
Message-ID: <20170808114625.GA13532@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Authenticated-Sender: thomas@m3y3r.de
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 286
Lines: 12

Hi,

did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel
build with an included ramdisk?

As fas as I understand you must expliclity add rootfstype=ramfs to the kernel
command line to boot from the included ramfsdisk?

bug or feature?

with kind regards
thomas