From: Greg KH <gregkh@linuxfoundation.org>
To: Doug Crawford <dcrawford@zonoff.com>
Cc: "ltsi-dev@lists.linuxfoundation.org"
<ltsi-dev@lists.linuxfoundation.org>,
"fuego@lists.linuxfoundation.org"
<fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] [LTSI-dev] Value of the Fuego to kernel "integrators"?
Date: Fri, 23 Sep 2016 17:05:03 +0200 [thread overview]
Message-ID: <20160923150503.GC13744@kroah.com> (raw)
In-Reply-To: <0FE76768-B446-4079-91CE-7A0F6A3B0F7C@zonoff.com>
On Fri, Sep 23, 2016 at 10:09:02AM -0400, Doug Crawford via LTSI-dev wrote:
> A perception in our organization is that Fuego is intended for kernel
> developers in the development of long term supported kernels.
> We are more “kernel integrators”; we pick up LTS kernels through
> Yocto, and integrate them with our choice of file system and device
> drivers.
What filesystems and device drivers do you use that are not already
upstream in the kernel.org releases? Need any help getting them merged
properly?
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-23 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 4:29 [Fuego] Fuego test_pre_check bug Bird, Timothy
2016-09-23 14:09 ` [Fuego] Value of the Fuego to kernel "integrators"? Doug Crawford
2016-09-23 15:05 ` Greg KH [this message]
2016-09-23 16:11 ` [Fuego] Failure on trial run of Fuego Doug Crawford
2016-09-23 16:46 ` Bird, Timothy
2016-09-23 17:29 ` Doug Crawford
2016-09-23 18:36 ` [Fuego] [LTSI-dev] " Bird, Timothy
2016-09-23 18:47 ` Doug Crawford
2016-09-23 18:57 ` Bird, Timothy
2016-09-23 19:24 ` Doug Crawford
2016-09-23 20:52 ` Doug Crawford
2016-09-26 21:22 ` Doug Crawford
2016-09-27 19:14 ` Bird, Timothy
2016-09-27 21:29 ` Doug Crawford
2016-09-23 17:20 ` [Fuego] [LTSI-dev] Value of the Fuego to kernel "integrators"? Doug Crawford
2016-09-23 17:30 ` Bird, Timothy
2016-09-23 18:29 ` Doug Crawford
2016-09-23 18:47 ` Bird, Timothy
2016-09-23 19:19 ` Doug Crawford
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=20160923150503.GC13744@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dcrawford@zonoff.com \
--cc=fuego@lists.linuxfoundation.org \
--cc=ltsi-dev@lists.linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.