{"id":8225,"date":"2019-01-16T13:57:51","date_gmt":"2019-01-16T13:57:51","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw92\/?p=8225"},"modified":"2019-03-07T22:50:24","modified_gmt":"2019-03-07T22:50:24","slug":"linux-today-linux-5-0-rc2","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/01\/16\/linux-today-linux-5-0-rc2\/","title":{"rendered":"Linux Today – Linux 5.0 rc2"},"content":{"rendered":"

Jan 13, 2019, 22:00 (0 Talkback[s]<\/a>)<\/p>\n

(Other stories by Linus Torvalds<\/a>)<\/p>\n

So the merge window had somewhat unusual timing with the holidays, and
\nI was afraid that would affect stragglers in rc2, but honestly, that
\ndoesn’t seem to have happened much. rc2 looks pretty normal.<\/p>\n

Were there some missing commits that missed the merge window? Yes. But<\/p>\n

no more than usual. Things look pretty normal.<\/p>\n

What’s a bit abnormal is that I’m traveling again, and so for me it’s<\/p>\n

a Monday release, but it’s (intentionally) the usual “Sunday
\nafternoon” release schedule back home. I’m trying to not surprise
\npeople too much.<\/p>\n

As to actual changes: all looks fairly normal. Yes, there’s a fair<\/p>\n

number of perf tooling updates, so that certainly stands out in the
\ndiffstat, but if you ignore the tooling and just look at the kernel,
\nit’s about two thirds drivers (networking, gpu, block, scsi..), with
\nthe rest being the usual mix of arch updates (ARM, RISC-V, x86, csky),
\nwith some filesystem (btrfs, cifs) and vm fixes.<\/p>\n

Go test,<\/p>\n

Linus<\/p>\n

Complete Story<\/a><\/p>\n

Related Stories:<\/p>\n