kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "陈 明政" <chen.mingzheng@outlook.com>
To: Greg KH <greg@kroah.com>,
	"kernelnewbies@kernelnewbies.org"
	<kernelnewbies@kernelnewbies.org>
Subject: Re: How to track the source tree of kernel
Date: Thu, 19 May 2022 11:14:54 +0000	[thread overview]
Message-ID: <TYCPR01MB57438B40B02F26DA4E8BD2E381D09@TYCPR01MB5743.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <YoUOCCm8d/p8JYfx@kroah.com>


[-- Attachment #1.1: Type: text/plain, Size: 2611 bytes --]

Hi Greg,

Sorry for the late reply, and the rude action before. I' m not quite familiar with the email rules, I will pay attention to it.

What I'm trying to do is to become a kernel developer, especially a driver developer. Maybe this is a more general object and lacks of clear steps. So I want to learn about the work flow ofkernel development to decompose the object.

And, I think, maybe the first step is to catch up with a branch of kernel source, for which I setup a raspi to track the kernel source daily with the help of crontab, and compile the kernel when there is a new commit and send an email to get a notification. Next, I should develop on the specific branch, and learn how to submit a patch to kernel.

But now, I'm confused that there so many branches in linux kernel source and other linux distribution source such as raspberrypi/linux.git, and I only know about how to submit a patch to kernel from kernel documents or kernelnewbies or other websites. Can I just work on a specific platform and submit a patch to kernel?

I currently work on i.mx6 platform and have a raspi4b for learning. Based on the linux SDK from board supplier, l developed some camera drivers. The SDK contains a dirty 4.1.15 kernel source, a uboot, anda prebuild rootfs archive. and the SDK is not controlled by a git, it's just an archive.

Supposed now, I know how to submit a patch to which branch, is therep any tests need to be run before I submit? or is there a requirement for writing a test program to test my driver first?

Could you give me some advices on what should I do next, or is l going toward a wrong direction?

Thanks in advance,

chen.

________________________________
发件人: Greg KH <greg@kroah.com>
发送时间: 2022年5月18日星期三 23:17
收件人: chen.mingzheng <chen.mingzheng@outlook.com>
抄送: kernelnewbies@kernelnewbies.org <kernelnewbies@kernelnewbies.org>
主题: Re: How to track the source tree of kernel

On Wed, May 18, 2022 at 10:47:59PM +0800, chen.mingzheng wrote:
> Hi Guys,
>
> Sorry to bother you all. I'm just starting learning linux with a rpi4b. I
> found the raspi source tree have many branches, which are different from the
> kernel source tree, which also have many branches. I want to know how should
> I track the source code. should I track all branches from the remote repo,
> or just stick to a specific branch? How did you do so that you can catch up
> to lastest kernel?

It all depends on what you want to do as to what tree/branch to work off
of and to track.

So, what exactly do you want to do?

thanks,

greg k-h


[-- Attachment #1.2: Type: text/html, Size: 5202 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2022-05-19 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 14:47 How to track the source tree of kernel chen.mingzheng
2022-05-18 15:17 ` Greg KH
2022-05-19 11:14   ` 陈 明政 [this message]
2022-05-19 14:53     ` Fox Chen

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=TYCPR01MB57438B40B02F26DA4E8BD2E381D09@TYCPR01MB5743.jpnprd01.prod.outlook.com \
    --to=chen.mingzheng@outlook.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@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).