Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751497AbdIQNv0 (ORCPT ); Sun, 17 Sep 2017 09:51:26 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:46617 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751282AbdIQNvX (ORCPT ); Sun, 17 Sep 2017 09:51:23 -0400 X-ME-Sender: X-Sasl-enc: tSJJEtZA+rLJpWXF04EJBp5BJMCG4/BA1lbMPl1HPGe6 1505656282 Date: Sun, 17 Sep 2017 10:51:19 -0300 From: Henrique de Moraes Holschuh To: Rob Landley Cc: Christophe LEROY , Michael Ellerman , Stephen Rothwell , sachinp , mhocko@suse.com, peterz@infradead.org, viresh.kumar@linaro.org, Benjamin Tissoires , mingo@kernel.org, lokeshvutla@ti.com, Abdul Haleem , linux-input@vger.kernel.org, thomas.lendacky@amd.com, lauraa@codeaurora.org, keescook@chromium.org, Jiri Kosina , rostedt@goodmis.org, linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, tglx@linutronix.de, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, tj@kernel.org, Andrew Morton , linuxppc-dev Subject: Re: [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT Message-ID: <20170917135119.nqo6dffx2zuqh36l@khazad-dum.debian.net> References: <1495700957.9020.43.camel@abdul.in.ibm.com> <8760gp9jjl.fsf@concordia.ellerman.id.au> <20170526072437.46499fbd@canb.auug.org.au> <87a7e82d-0af5-7f9e-6bd6-7e28b238e866@landley.net> <87r2z86ykt.fsf@concordia.ellerman.id.au> <4aa9cb26-f868-0720-e5c8-3c4e08afad20@landley.net> <3ba5ddc7-d1a2-7f54-0a26-0752f3975226@c-s.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Fingerprint1: 4096R/0x0BD9E81139CB4807: C467 A717 507B BAFE D3C1 6092 0BD9 E811 39CB 4807 User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 22 On Sat, 16 Sep 2017, Rob Landley wrote: > So, I added a workaround with a printk in hopes of embarassing them into > someday fixing it. Oh, it will be fixed in Debian alright. I am just waiting the issue to settle a bit to file the bug reports, or maybe even send in the Debian patches myself (note that I am not responsible for the code in question, so I am not wearing a brown paperbag at this time). Even if I didn't do it, there are several other Debian Developers reading LKML that could do it (provided they noticed this specific thread and are aware of the situation) :p I can even push for the fixes to be accepted into the stable and oldstable branches of Debian, but that can take anything from a few weeks to several months, due to the way our stable releases work. But it would eventually happen. Whether such fixes will ever make it to LTS branches, especially Ubuntu's, *that* I don't know. -- Henrique Holschuh