From: 583241212@qq.com (Aric)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to contact to Greg.
Date: Thu, 12 May 2016 19:14:42 +0800 [thread overview]
Message-ID: <tencent_6DFC4AAA192F2C2B1C3FFFDE@qq.com> (raw)
In-Reply-To: <127484.1462987951@turing-police.cc.vt.edu>
Yeah, that sounds good. Who know Greg's e-mail,or where to find him?
------------------ Original ------------------
From: "Valdis.Kletnieks";<Valdis.Kletnieks@vt.edu>;
Date: Thu, May 12, 2016 01:32 AM
To: "Aric"<583241212@qq.com>;
Cc: "Robert P. J. Day"<rpjday@crashcourse.ca>; "kernelnewbies"<kernelnewbies@kernelnewbies.org>;
Subject: Re: How to fast master kernel
On Wed, 11 May 2016 12:26:17 +0800, "Aric" said:
> But for each board, it have dedicated kernel code package. For example, what
> I want to do first, it I can write kernel drivers and kernel code freely. I can
> easily add a I2C (AT24C02) device and finished its driver in a short time.
Wel, that's only actually helpful for the kernel if somebody's already
done the port to that board (which it seems they have, since it already
has a kernel package), and failed to add an I2C driver already.
The other thing that you could do that would benefit the kernel is to take
the vendor's code (which is probably some ancient creeping horror like 3.4
or even a 2.6.something), and get the drivers up to 4.6 level and get them
upstreamed.
Greg KH is almost certainly reading this, and he *loves* helping get
drivers into the main kernel :)
Greg, meet Aric. Aric, meet Greg. :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160512/43e5ac68/attachment.html
next prev parent reply other threads:[~2016-05-12 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_11C81A8B074E9D774D6DCA28@qq.com>
2016-05-11 17:32 ` How to fast master kernel Valdis.Kletnieks at vt.edu
2016-05-12 11:14 ` Aric [this message]
2016-05-13 8:34 ` How to contact to Greg Greg KH
2016-05-13 8:55 ` Valdis.Kletnieks at vt.edu
2016-05-13 8:59 ` Aric
2016-05-13 12:53 ` Sudip Mukherjee
2016-05-13 13:05 ` Robert P. J. Day
2016-05-13 13:08 ` =?gb18030?B?u9i4tKO6SG93IHRvIGNvbnRhY3QgdG8gR3JlZy4=?= =?gb18030?B?QXJpYw==?=
2016-05-13 13:17 ` 回复：How to contact to Greg Colin Vidal
2016-05-13 13:22 ` Greg KH
2016-05-13 17:39 ` ?c8???How " Valdis.Kletnieks at vt.edu
2016-05-13 16:25 How " walkerlala
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=tencent_6DFC4AAA192F2C2B1C3FFFDE@qq.com \
--to=583241212@qq.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).