From: Greg KH <greg@kroah.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Sandy Harris <sandyinchina@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, John Denker <jsd@av8n.com>
Subject: Re: Read/write file from random(4) driver
Date: Sat, 18 Apr 2015 20:56:00 +0200 [thread overview]
Message-ID: <20150418185600.GC30508@kroah.com> (raw)
In-Reply-To: <20150418170219.GA25265@thunk.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
prev parent reply other threads:[~2015-04-18 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 15:28 Read/write file from random(4) driver Sandy Harris
2015-04-18 17:02 ` Theodore Ts'o
2015-04-18 18:56 ` Greg KH [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=20150418185600.GC30508@kroah.com \
--to=greg@kroah.com \
--cc=jsd@av8n.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=tytso@mit.edu \
/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