kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* How to track the source tree of kernel
@ 2022-05-18 14:47 chen.mingzheng
  2022-05-18 15:17 ` Greg KH
  0 siblings, 1 reply; 4+ messages in thread
From: chen.mingzheng @ 2022-05-18 14:47 UTC (permalink / raw)
  To: kernelnewbies

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?

Thanks in advance!

Sincerely,
A Linux newbies.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to track the source tree of kernel
  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   ` 陈 明政
  0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2022-05-18 15:17 UTC (permalink / raw)
  To: chen.mingzheng; +Cc: kernelnewbies

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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to track the source tree of kernel
  2022-05-18 15:17 ` Greg KH
@ 2022-05-19 11:14   ` 陈 明政
  2022-05-19 14:53     ` Fox Chen
  0 siblings, 1 reply; 4+ messages in thread
From: 陈 明政 @ 2022-05-19 11:14 UTC (permalink / raw)
  To: Greg KH, kernelnewbies


[-- 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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to track the source tree of kernel
  2022-05-19 11:14   ` 陈 明政
@ 2022-05-19 14:53     ` Fox Chen
  0 siblings, 0 replies; 4+ messages in thread
From: Fox Chen @ 2022-05-19 14:53 UTC (permalink / raw)
  To: 陈 明政; +Cc: Greg KH, kernelnewbies

Hi,

On Thu, May 19, 2022 at 7:15 PM 陈 明政 <chen.mingzheng@outlook.com> wrote:
>
> 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.
>

This course may be helpful for you to clear things up.
https://training.linuxfoundation.org/training/a-beginners-guide-to-linux-kernel-development-lfd103


thanks,
fox

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-05-19 14:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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   ` 陈 明政
2022-05-19 14:53     ` Fox Chen

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).