pub/scm/linux/kernel/git/arnd/playground.git  about / heads / tags
Fun projects that arnd has been hacking on
$ git log --pretty=format:'%h %s (%cs)%d'
69973b830859b Linux 4.9 (2016-12-11)
	(HEAD -> master)
2e4333c14de06 Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus (2016-12-11)
ba735155b9647 MIPS: Lantiq: Fix mask of GPE frequency (2016-12-11)
edb6fa1a6452e MIPS: Return -ENODEV from weak implementation of rtc_mips_set_time (2016-12-11)
045169816b31b Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 (2016-12-10)
cd6628953e421 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2016-12-10)
d33695fbfab73 net: mlx5: Fix Kconfig help text (2016-12-09)
ab4e4c07aca7b net: smsc911x: back out silently on probe deferrals (2016-12-09)
7b5967389f5a8 ibmveth: set correct gso_size and gso_type (2016-12-09)
810ac7b7558d7 Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm (2016-12-09)
...

$ git cat-file blob HEAD:README
        Linux kernel release 4.x <http://kernel.org/>

These are the release notes for Linux version 4.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.

WHAT IS LINUX?

  Linux is a clone of the operating system Unix, written from scratch by
  Linus Torvalds with assistance from a loosely-knit team of hackers across
  the Net. It aims towards POSIX and Single UNIX Specification compliance.

  It has all the features you would expect in a modern fully-fledged Unix,
  including true multitasking, virtual memory, shared libraries, demand
  loading, shared copy-on-write executables, proper memory management,
  and multistack networking including IPv4 and IPv6.

  It is distributed under the GNU General Public License - see the
  accompanying COPYING file for more details.

ON WHAT HARDWARE DOES IT RUN?

  Although originally developed first for 32-bit x86-based PCs (386 or higher),
  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
  Xtensa, Tilera TILE, AVR32, ARC and Renesas M32R architectures.

  Linux is easily portable to most general-purpose 32- or 64-bit architectures
  as long as they have a paged memory management unit (PMMU) and a port of the
  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
  also been ported to a number of architectures without a PMMU, although
  functionality is then obviously somewhat limited.
  Linux has also been ported to itself. You can now run the kernel as a
  userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

 - There is a lot of documentation available both in electronic form on
   the Internet and in books, both Linux-specific and pertaining to
   general UNIX questions.  I'd recommend looking into the documentation
   subdirectories on any Linux FTP site for the LDP (Linux Documentation
   Project) books.  This README is not meant to be documentation on the
   system: there are much better sources available.

 - There are various README files in the Documentation/ subdirectory:
   these typically contain kernel-specific installation notes for some
   drivers for example. See Documentation/00-INDEX for a list of what
   is contained in each file.  Please read the Changes file, as it
   contains information about the problems, which may result by upgrading
   your kernel.

 - The Documentation/DocBook/ subdirectory contains several guides for
   kernel developers and users.  These guides can be rendered in a
   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.
   After installation, "make psdocs", "make pdfdocs", "make htmldocs",
   or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

 - If you install the full sources, put the kernel tarball in a
   directory where you have permissions (e.g. your home directory) and
   unpack it:

     xz -cd linux-4.X.tar.xz | tar xvf -

   Replace "X" with the version number of the latest kernel.

   Do NOT use the /usr/src/linux area! This area has a (usually
   incomplete) set of kernel headers that are used by the library header
   files.  They should match the library, and not get messed up by
   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 4.x releases by patching.  Patches are
   distributed in the xz format.  To install by patching, get all the
   newer patch files, enter the top level directory of the kernel source
   (linux-4.X) and execute:

     xz -cd ../patch-4.x.xz | patch -p1

   Replace "x" for all versions bigger than the version "X" of your current
   source tree, _in_order_, and you should be ok.  You may want to remove
   the backup files (some-file-name~ or some-file-name.orig), and make sure
   that there are no failed patches (some-file-name# or some-file-name.rej).
   If there are, either you or I have made a mistake.

   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 4.x kernel.  For example, if your base kernel is 4.0
   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
   patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
   Documentation/applying-patches.txt

   Alternatively, the script patch-kernel can be used to automate this
   process.  It determines the current kernel version and applies any
   patches found.

     linux/scripts/patch-kernel linux

   The first argument in the command above is the location of the
   kernel source.  Patches are applied from the current directory, but
   an alternative directory can be specified as the second argument.

 - Make sure you have no stale .o files and dependencies lying around:

     cd linux
     make mrproper

   You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

   Compiling and running the 4.x kernels requires up-to-date
   versions of various software packages.  Consult
   Documentation/Changes for the minimum version numbers required
   and how to get updates for these packages.  Beware that using
   excessively old versions of these packages can cause indirect
   errors that are very difficult to track down, so don't assume that
   you can just update packages when obvious problems arise during
   build or operation.

BUILD directory for the kernel:

   When compiling the kernel, all output files will per default be
   stored together with the kernel source code.
   Using the option "make O=output/dir" allows you to specify an alternate
   place for the output files (including .config).
   Example:

     kernel source code: /usr/src/linux-4.X
     build directory:    /home/name/build/kernel

   To configure and build the kernel, use:

     cd /usr/src/linux-4.X
     make O=/home/name/build/kernel menuconfig
     make O=/home/name/build/kernel
     sudo make O=/home/name/build/kernel modules_install install

   Please note: If the 'O=output/dir' option is used, then it must be
   used for all invocations of make.

CONFIGURING the kernel:

   Do not skip this step even if you are only upgrading one minor
   version.  New configuration options are added in each release, and
   odd problems will turn up if the configuration files are not set up
   as expected.  If you want to carry your existing configuration to a
   new version with minimal work, use "make oldconfig", which will
   only ask you for the answers to new questions.

 - Alternative configuration commands are:

     "make config"      Plain text interface.

     "make menuconfig"  Text based color menus, radiolists & dialogs.

     "make nconfig"     Enhanced text based color menus.

     "make xconfig"     Qt based configuration tool.

     "make gconfig"     GTK+ based configuration tool.

     "make oldconfig"   Default all questions based on the contents of
                        your existing ./.config file and asking about
                        new config symbols.

     "make silentoldconfig"
                        Like above, but avoids cluttering the screen
                        with questions already answered.
                        Additionally updates the dependencies.

     "make olddefconfig"
                        Like above, but sets new symbols to their default
                        values without prompting.

     "make defconfig"   Create a ./.config file by using the default
                        symbol values from either arch/$ARCH/defconfig
                        or arch/$ARCH/configs/${PLATFORM}_defconfig,
                        depending on the architecture.

     "make ${PLATFORM}_defconfig"
                        Create a ./.config file by using the default
                        symbol values from
                        arch/$ARCH/configs/${PLATFORM}_defconfig.
                        Use "make help" to get a list of all available
                        platforms of your architecture.

     "make allyesconfig"
                        Create a ./.config file by setting symbol
                        values to 'y' as much as possible.

     "make allmodconfig"
                        Create a ./.config file by setting symbol
                        values to 'm' as much as possible.

     "make allnoconfig" Create a ./.config file by setting symbol
                        values to 'n' as much as possible.

     "make randconfig"  Create a ./.config file by setting symbol
                        values to random values.

     "make localmodconfig" Create a config based on current config and
                           loaded modules (lsmod). Disables any module
                           option that is not needed for the loaded modules.

                           To create a localmodconfig for another machine,
                           store the lsmod of that machine into a file
                           and pass it in as a LSMOD parameter.

                   target$ lsmod > /tmp/mylsmod
                   target$ scp /tmp/mylsmod host:/tmp

                   host$ make LSMOD=/tmp/mylsmod localmodconfig

                           The above also works when cross compiling.

     "make localyesconfig" Similar to localmodconfig, except it will convert
                           all module options to built in (=y) options.

   You can find more information on using the Linux kernel config tools
   in Documentation/kbuild/kconfig.txt.

 - NOTES on "make config":

    - Having unnecessary drivers will make the kernel bigger, and can
      under some circumstances lead to problems: probing for a
      nonexistent controller card may confuse your other controllers

    - A kernel with math-emulation compiled in will still use the
      coprocessor if one is present: the math emulation will just
      never get used in that case.  The kernel will be slightly larger,
      but will work on different machines regardless of whether they
      have a math coprocessor or not.

    - The "kernel hacking" configuration details usually result in a
      bigger or slower kernel (or both), and can even make the kernel
      less stable by configuring some routines to actively try to
      break bad code to find kernel problems (kmalloc()).  Thus you
      should probably answer 'n' to the questions for "development",
      "experimental", or "debugging" features.

COMPILING the kernel:

 - Make sure you have at least gcc 3.2 available.
   For more information, refer to Documentation/Changes.

   Please note that you can still run a.out user programs with this kernel.

 - Do a "make" to create a compressed kernel image. It is also
   possible to do "make install" if you have lilo installed to suit the
   kernel makefiles, but you may want to check your particular lilo setup first.

   To do the actual install, you have to be root, but none of the normal
   build should require that. Don't take the name of root in vain.

 - If you configured any of the parts of the kernel as `modules', you
   will also have to do "make modules_install".

 - Verbose kernel compile/build output:

   Normally, the kernel build system runs in a fairly quiet mode (but not
   totally silent).  However, sometimes you or other kernel developers need
   to see compile, link, or other commands exactly as they are executed.
   For this, use "verbose" build mode.  This is done by passing
   "V=1" to the "make" command, e.g.

     make V=1 all

   To have the build system also tell the reason for the rebuild of each
   target, use "V=2".  The default is "V=0".

 - Keep a backup kernel handy in case something goes wrong.  This is
   especially true for the development releases, since each new release
   contains new code which has not been debugged.  Make sure you keep a
   backup of the modules corresponding to that kernel, as well.  If you
   are installing a new kernel with the same version number as your
   working kernel, make a backup of your modules directory before you
   do a "make modules_install".

   Alternatively, before compiling, use the kernel config option
   "LOCALVERSION" to append a unique suffix to the regular kernel version.
   LOCALVERSION can be set in the "General Setup" menu.

 - In order to boot your new kernel, you'll need to copy the kernel
   image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
   to the place where your regular bootable kernel is found.

 - Booting a kernel directly from a floppy without the assistance of a
   bootloader such as LILO, is no longer supported.

   If you boot Linux from the hard drive, chances are you use LILO, which
   uses the kernel image as specified in the file /etc/lilo.conf.  The
   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
   /boot/bzImage.  To use the new kernel, save a copy of the old image
   and copy the new image over the old one.  Then, you MUST RERUN LILO
   to update the loading map! If you don't, you won't be able to boot
   the new kernel image.

   Reinstalling LILO is usually a matter of running /sbin/lilo.
   You may wish to edit /etc/lilo.conf to specify an entry for your
   old kernel image (say, /vmlinux.old) in case the new one does not
   work.  See the LILO docs for more information.

   After reinstalling LILO, you should be all set.  Shutdown the system,
   reboot, and enjoy!

   If you ever need to change the default root device, video mode,
   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or
   alternatively the LILO boot options when appropriate).  No need to
   recompile the kernel to change these parameters.

 - Reboot with the new kernel and enjoy.

IF SOMETHING GOES WRONG:

 - If you have problems that seem to be due to kernel bugs, please check
   the file MAINTAINERS to see if there is a particular person associated
   with the part of the kernel that you are having trouble with. If there
   isn't anyone listed there, then the second best thing is to mail
   them to me (torvalds@linux-foundation.org), and possibly to any other
   relevant mailing-list or to the newsgroup.

 - In all bug-reports, *please* tell what kernel you are talking about,
   how to duplicate the problem, and what your setup is (use your common
   sense).  If the problem is new, tell me so, and if the problem is
   old, please try to tell me when you first noticed it.

 - If the bug results in a message like

     unable to handle kernel paging request at address C0000010
     Oops: 0002
     EIP:   0010:XXXXXXXX
     eax: xxxxxxxx   ebx: xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx
     esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx
     ds: xxxx  es: xxxx  fs: xxxx  gs: xxxx
     Pid: xx, process nr: xx
     xx xx xx xx xx xx xx xx xx xx

   or similar kernel debugging information on your screen or in your
   system log, please duplicate it *exactly*.  The dump may look
   incomprehensible to you, but it does contain information that may
   help debugging the problem.  The text above the dump is also
   important: it tells something about why the kernel dumped code (in
   the above example, it's due to a bad kernel pointer). More information
   on making sense of the dump is in Documentation/oops-tracing.txt

 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
   as is, otherwise you will have to use the "ksymoops" program to make
   sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
   This utility can be downloaded from
   ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
   Alternatively, you can do the dump lookup by hand:

 - In debugging dumps like the above, it helps enormously if you can
   look up what the EIP value means.  The hex value as such doesn't help
   me or anybody else very much: it will depend on your particular
   kernel setup.  What you should do is take the hex value from the EIP
   line (ignore the "0010:"), and look it up in the kernel namelist to
   see which kernel function contains the offending address.

   To find out the kernel function name, you'll need to find the system
   binary associated with the kernel that exhibited the symptom.  This is
   the file 'linux/vmlinux'.  To extract the namelist and match it against
   the EIP from the kernel crash, do:

     nm vmlinux | sort | less

   This will give you a list of kernel addresses sorted in ascending
   order, from which it is simple to find the function that contains the
   offending address.  Note that the address given by the kernel
   debugging messages will not necessarily match exactly with the
   function addresses (in fact, that is very unlikely), so you can't
   just 'grep' the list: the list will, however, give you the starting
   point of each kernel function, so by looking for the function that
   has a starting address lower than the one you are searching for but
   is followed by a function with a higher address you will find the one
   you want.  In fact, it may be a good idea to include a bit of
   "context" in your problem report, giving a few lines around the
   interesting one.

   If you for some reason cannot do the above (you have a pre-compiled
   kernel image or similar), telling me as much about your setup as
   possible will help.  Please read the REPORTING-BUGS document for details.

 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
   cannot change values or set break points.) To do this, first compile the
   kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
   clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

   After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
   You can now use all the usual gdb commands. The command to look up the
   point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
   with the EIP value.)

   gdb'ing a non-running kernel currently fails because gdb (wrongly)
   disregards the starting offset for which the kernel is compiled.

# heads (aka `branches'):
$ git for-each-ref --sort=-creatordate refs/heads \
	--format='%(HEAD) %(refname:short) %(subject) (%(creatordate:short))'
  highmem-7.4  mm: print pte in __print_bad_page_map_pgtable() (2026-11-14)
  next-merge-7.4 Merge branch 'highmem-7.4' into next-merge-7.4 (2026-11-12)
  kbuild-warnings-enable-7.4 kbuild: always enable Wunused-const-variable for gcc (2026-11-11)
  board-remove-7.4 i2c: remove unused acorn driver (2026-11-10)
  randconfig-7.3-next rtc: renesas: avouud -Wtautological-constant-out-of-range-compare warning (2026-09-19)
  config-gpio-legacy-7.3 [RFC] gpiolib: introduce gpio_name() helper (2026-09-04)
  config-gpio-legacy-7.2 [RFC] gpiolib: introduce gpio_name() helper (2026-06-30)
  abi-test     uapi: all other changes (2026-06-24)
  Wtautological-constant Makefile.warn: turn on -Wno-tautological-constant-out-of-range-compare (2026-06-05)
  x86-cpu-3    x86: simplify 32-bit instruction set selection (2026-05-22)
...

# tags:
$ git for-each-ref --sort=-creatordate refs/tags \
	--format='%(refname:short) %(subject) (%(creatordate:short))'
config-gpio-legacy-for-7.3 gpio: legacy interface cleanups for 7.3 (2026-07-24) tar.gz
arm-setfs-v4 ARM: kill CONFIG_SET_FS (2020-10-30) tar.gz
wimax-staging wimax: move to staging (2020-10-29) tar.gz
sh5-remove   sh: remove sh5 support (2020-04-25) tar.gz
compat-ioctl-fix compat-ioctl fix for v5.6 (2020-02-08) tar.gz
y2038-drivers-for-v5.6-signed y2038: core, driver and file system changes (2020-01-29) tar.gz
asm-generic-5.5 asm-generic: fixes for v5.5 (2020-01-14) tar.gz
block-ioctl-cleanup-5.6 block, scsi: final compat_ioctl cleanup (2020-01-03) tar.gz
block-ioctl-fixes-5.5 block: ioctl fixes for v5.5 (2019-12-17) tar.gz
y2038-alsa-v8-signed ALSA: Fix year 2038 issue for sound subsystem (2019-12-17) tar.gz
...

# associated public inboxes:
# (number on the left is used for dev purposes)
    1422508 lkml
     431725 stable
     375230 netdev
     284228 linux-arm-kernel
     154573 linux-devicetree
     121382 linux-wireless
     119082 dri-devel
      82940 linux-mm
      82310 linux-fsdevel
      81173 linuxppc-dev
      78429 linux-media
      73008 alsa-devel
      71920 linux-patches
      60428 kvm
      59310 intel-gfx
      54718 linux-scsi
      54353 amd-gfx
      51385 linux-arm-msm
      43944 linux-mips
      43856 linux-omap
      43761 linux-arch
      41461 linux-doc
      40438 linux-xfs
      38802 bpf
      36901 linux-rdma
      35388 linux-crypto
      34888 linux-pm
      34748 linux-nfs
      33367 linux-mediatek
      32958 linux-s390
      30650 linux-samsung-soc
      29961 linux-block
      29579 linux-riscv
      28885 linux-acpi
      28621 linux-perf-users
      27552 linux-renesas-soc
      27482 netfilter-devel
      26662 linux-gpio
      26307 linux-pci
      25864 linux-clk
      25778 linux-kselftest
      25484 linux-usb
      24879 linux-mtd
      24537 linux-iio
      24033 linux-tegra
      23474 linux-sh
      21749 sparclinux
      21261 linux-btrfs
      20366 linux-input
      20131 kernel-janitors
      19999 kvmarm
      18016 linux-ext4
      17949 linux-staging
      17482 linux-iommu
      17075 linux-cifs
      17059 linux-serial
      16869 linux-rockchip
      16845 linux-ide
      16554 xen-devel
      16338 linux-api
      16232 linux-fbdev
      15801 linux-mmc
      15692 linux-kbuild
      15681 intel-xe
      15389 virtualization
      14877 u-boot
      14872 linux-sound
      14391 linux-security-module
      13996 driverdev-devel
      13795 intel-wired-lan
      13550 linux-bluetooth
      13516 linux-spi
      13271 linux-parisc
      12771 platform-driver-x86
      12563 linux-amlogic
      12466 linux-i2c
      12371 qemu-devel
      12215 linux-um
      11932 ceph-devel
      11891 linux-f2fs-devel
      10958 linux-alpha
      10478 dm-devel
      10341 linux-ia64
      10184 linux-m68k
       9655 loongarch
       9641 linux-trace-kernel
       9501 cgroups
       9384 linux-sunxi
       9239 linux-snps-arc
       9111 nouveau
       9043 linux-nvme
       8809 nvdimm
       8358 linux-can
       7799 linux-efi
       7769 linux-hwmon
       7520 imx
       7488 linux-raid
       7216 cluster-devel
       7183 linux-hardening
       7162 rust-for-linux
       7022 linux-rtc
       7012 cip-dev
       6926 linux-watchdog
       6873 linux-hexagon
       6625 lustre-devel
       6524 batman
       6505 containers
       6503 openrisc
       6417 linux-integrity
       6308 dmaengine
       6265 selinux
       6221 rcu
       6208 ocfs2-devel
       6046 io-uring
       5974 kvm-ppc
       5940 llvm
       5615 linux-pwm
       5593 linux-csky
       5527 linux-nvdimm
       5517 linux-rt-users
       5471 linux-leds
       5235 linux-next
       5189 mptcp
       4987 linux-hyperv
       4854 linux-sctp
       4817 kernel-hardening
       4797 linux-phy
       4784 linux-cxl
       4461 bridge
       4399 linux-remoteproc
       4312 outreachy
       4247 ath10k
       4219 kexec
       4064 dpdk-dev
       4063 soc
       4018 linux-modules
       3993 git
       3972 linux-unionfs
       3962 b4-sent
       3935 buildroot
       3908 linux-erofs
       3896 keyrings
       3748 lm-sensors
       3655 linux-nilfs
       3503 linux-wpan
       3401 linux-fscrypt
       3277 target-devel
       3145 ath11k
       3123 asahi
       3067 linux-edac
       3040 ath12k
       3023 linux-bcache
       2734 openbmc
       2636 damon
       2504 chrome-platform
       2502 v9fs
       2354 lvs-devel
       2318 openembedded-core
       2295 ath9k-devel
       2274 linux-hams
       2229 phone-devel
       2152 sched-ext
       2026 ntfs3
       1947 linux-audit
       1826 linux-bcachefs
       1772 netfs
       1762 linux-fpga
       1692 linux-kernel-mentees
       1659 openembedded-devel
       1637 linux-coco
       1591 cpufreq
       1574 gfs2
       1533 dccp
       1482 linux-trace-devel
       1463 ecryptfs
       1421 reiserfs-devel
       1392 b43-dev
       1258 historical-speck
       1241 live-patching
       1223 linux-sgx
       1135 linux-x25
       1133 driver-core
       1069 ntb
       1011 fsverity
        974 kvm-riscv
        965 linux-aspeed
        959 linux-metag
        949 linux-i3c
        913 linux-spdx
        910 fstests
        898 nova-gpu
        895 oe-kbuild-all
        887 spacemit
        842 ltp
        790 linux-sparse
        789 audit
        760 autofs
        709 linux-man
        702 igt-dev
        694 linux-rt-devel
        684 netfilter
        680 linux-ppp
        675 cocci
        670 arm-scmi
        640 lvm-devel
        610 linux-toolchains
        566 regressions
        555 qemu-riscv
        537 tpmdd-devel
        504 sophgo
        488 linux-oxnas
        477 yocto
        470 oe-lkp
        448 workflows
        421 virtio-dev
        415 wireguard
        413 brcm80211
        407 acpica-devel
        405 oe-linux-nfc
        384 kernel-tls-handshake
        364 mhi
        311 linux-nfc
        291 u-boot-amlogic
        270 fuse-devel
        262 lttng-dev
        235 yocto-meta-ti
        225 bitbake-devel
        224 grub-devel
        221 mm-commits
        220 yocto-meta-arago
        202 xfs-stable
        198 backports
        194 ofono
        176 mfd
        171 util-linux
        169 kernel-testers
        166 yocto-meta-freescale
        165 xenomai
        164 fio
        159 poky
        154 op-tee
        151 linux-embedded
        149 xdp-newbies
        149 devicetree-compiler
        149 kvm-ia64
        147 yocto-meta-arm
        143 kernelci
        134 x86-cpuid
        133 virtio-fs
        124 linux-kernel-announce
        112 sashiko-reviews
        108 iwd
        104 lkmm
         99 trinity
         94 ntfs
         93 yocto-meta-virtualization
         90 linux-laptop
         86 kernelnewbies
         83 yocto-docs
         80 initramfs
         76 selinux-refpolicy
         76 linux-btrace
         73 ksummit
         72 linux-hotplug
         64 ksummit-discuss
         61 fuego
         60 perfbook
         59 linux-firmware
         57 ell
         57 yocto-toaster
         53 dwarves
         49 yocto-patches
         46 qemu-arm
         45 barebox
         42 stable-rt
         41 timestamp
         38 drbd-dev
         37 openvpn-devel
         36 kdevops
         34 virtio-comment
         31 wireless-regdb
         31 rpdfs-devel
         29 linux-console
         28 devicetree-spec
         27 linux-debuggers
         27 powertop
         25 linux-lvm
         23 oe-kbuild
         22 syzbot
         20 exfat
         19 connman
         18 dash
         17 linux-safety
         16 linux-dash
         16 ultralinux
         14 dtrace
         13 linux-trace-users
         13 hail-devel
         11 mailbox
         10 kbd
         10 opensbi
          9 radiotap
          9 smatch
          8 tools
          8 tech-board-discuss
          8 qemu-rust
          6 ccan
          6 linux-newbie
          6 criu
          5 keys
          5 linux-numa
          5 accel-config
          4 dm-crypt
          4 linux-msdos
          4 lartc
          3 stgt
          3 linux-smp
          3 tpm2
          3 sashiko
          2 linux-dwarves
          2 oe-chipsec
          1 signatures
          1 linux-bugs
          1 cti-tac
          1 linux-config
          1 linux-8086
          1 mlmmj
          1 spdk
          1 coconut-svsm
          1 qemu-trivial

git clone https://yhbt.net/lore/pub/scm/linux/kernel/git/arnd/playground.git