From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about porting over magic lantern kernel hardware support to mainline
Date: Wed, 22 Apr 2015 22:09:39 -0400 [thread overview]
Message-ID: <55385463.7090201@gmail.com> (raw)
Greetings All,
I was wondering about reading this forum page,http://www.magiclantern.fm/forum/index.php?topic=14847.0;prev_next=next#new
if porting over magic lantern's change to the main line kernel is a good idea or does it need to be kept separate.Honestly,
from my personal experience high resolution cameras running Linux may be of great use to thousands of independent film makers
worldwide and it would be easier for vendors of said cameras to use the main line kernel for this and not a patched vendor
kernel for supporting there hardware. If the camera vendors are very closed mine, then I would see no point in doing this.
Anyhow please let me known of any options on main lining this or keeping it separate.
Thanks,
Nick
reply other threads:[~2015-04-23 2:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55385463.7090201@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).