All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Lafan Mining <lkfan@protonmail.com>
Cc: Greg KH <greg@kroah.com>,
	"kernelnewbies@kernelnewbies.org"
	<kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel upstream compile error at drivers/staging/media
Date: Fri, 10 Sep 2021 12:52:00 +0200	[thread overview]
Message-ID: <CAKXUXMyKKG7KdmfW7yRcT1SjXLFcAtXz-Z0B5-G=Cxm2F6PcMw@mail.gmail.com> (raw)
In-Reply-To: <IKHOSvAlC3X8UV5pNj4doeEQGnFAFp9VT25ATHQo1LOl8gWxrlyod6gX7aX86RYQDwmj8FiyhPQ8TJlR3CdXnVGOQWWI3EiUCRajQeU8smg=@protonmail.com>

On Fri, Sep 10, 2021 at 12:31 PM Lafan Mining <lkfan@protonmail.com> wrote:
>
> On Wednesday, September 8th, 2021 at 7:19 PM, Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> > integration tree, and hence in linux-next
>
> So generally to get the latest kernel version that is going to be merged into master soon is using linux-next's master?

That is roughly right; more details are here:
https://www.kernel.org/doc/html/latest/process/2.Process.html#next-trees

Most of it is still correct; some of it might be outdated.

E.g., I am not completely sure if Andrew Morton still does this
mentioned in the documentation: "The -mm tree integrates patches from
a long list of subsystem trees", or if most integration from a long
list of subsystem trees is nowadays completely done by Stephen
Rothwell in linux-next.

Also, possibly the statistics is outdated here in this statement: "In
a typical development cycle, approximately 5-10% of the patches going
into the mainline get there via -mm." One might need to check the
current numbers and update the percentage here.

Feel free to do a bit more research if you are interested and send a
patch to update the Documentation on what you learned.


Lukas

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

      reply	other threads:[~2021-09-10 10:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  9:39 Kernel upstream compile error at drivers/staging/media Lafan Mining
2021-09-08  9:50 ` Greg KH
2021-09-08 10:02   ` Lafan Mining
2021-09-08 10:06     ` Greg KH
2021-09-08 10:36       ` Lafan Mining
2021-09-08 15:59   ` Lafan Mining
2021-09-08 16:19     ` Lukas Bulwahn
2021-09-10 10:31       ` Lafan Mining
2021-09-10 10:52         ` Lukas Bulwahn [this message]

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='CAKXUXMyKKG7KdmfW7yRcT1SjXLFcAtXz-Z0B5-G=Cxm2F6PcMw@mail.gmail.com' \
    --to=lukas.bulwahn@gmail.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=lkfan@protonmail.com \
    /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.