From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754360AbbDRS4L (ORCPT ); Sat, 18 Apr 2015 14:56:11 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:58434 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754274AbbDRS4G (ORCPT ); Sat, 18 Apr 2015 14:56:06 -0400 X-Sasl-enc: KtKfVdviuJd+DWaSfqJbM9zddRXrQoex0pGVyASROi/Y 1429383362 Date: Sat, 18 Apr 2015 20:56:00 +0200 From: Greg KH To: "Theodore Ts'o" , Sandy Harris , LKML , John Denker Subject: Re: Read/write file from random(4) driver Message-ID: <20150418185600.GC30508@kroah.com> References: <20150418170219.GA25265@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150418170219.GA25265@thunk.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 18, 2015 at 01:02:19PM -0400, Theodore Ts'o wrote: > (Assuming you can get the embedded developers to use the latest > version of the userspace distributions / frameworks, granted, which is > not at all guaranteed, but they are more likely to use newer userspace > than they are the latest kernels, due to the device driver issue.) What "device driver issue" is keeping anyone on such old and obsolete kernel versions? BSPs that never submitted their code upstream? Or something else that is broken and no one has told us about? thanks, greg k-h