pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git  about / heads / tags
f2fs backport support
$ git log --pretty=format:'%h %s (%cs)%d'
c8d2bc9bc39eb Linux 4.8 (2016-10-02)
	(HEAD -> master, tag: v4.8)
f76d9c61d9134 Merge branch 'fixes' of git:// (2016-10-02)
117e5e9c4cfcb ARM: 8618/1: decompressor: reset ttbcr fields to use TTBR0 on ARMv7 (2016-10-02)
be67d60ba944b Merge branch 'x86-urgent-for-linus' of git:// (2016-10-02)
66188fb11a826 Merge branch 'upstream' of git:// (2016-10-02)
0c7fc30f18220 Merge git:// (2016-10-02)
bb6bbc7ca2254 Merge git:// (2016-10-02)
6605d156bdfbb MIPS: CM: Fix mips_cm_max_vp_width for non-MT kernels on MT systems (2016-10-02)
f51fdffad5b77 Merge tag 'scsi-fixes' of git:// (2016-10-01)
2161a2a644a6d Merge branch 'for-linus' of git:// (2016-09-30)

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

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.


  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.


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


 - 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

   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.


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

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

    - Compiling the kernel with "Processor type" set higher than 386
      will result in a kernel that does NOT work on a 386.  The
      kernel will detect this on bootup, and give up.

    - 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/i386/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 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 (, 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> .
   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/i386/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))'
  linux-6.1.y  f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault (2024-03-14)
  linux-6.6.y  f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault (2024-03-14)
  linux-5.15.y f2fs: Avoid reading renamed directory if parent does not change (2024-01-12)
  linux-5.10.y f2fs: use finish zone command when closing a zone (2023-08-25)
  linux-5.4.y  f2fs: drop unnecessary arg for f2fs_ioc_*() (2023-02-27)
  linux-4.19.y f2fs: reset wait_ms to default if any of the victims have been selected (2022-12-12)
  linux-4.14.y f2fs: use onstack pages instead of pvec (2022-08-05)
  linux-5.10.y-mainline f2fs: use onstack pages instead of pvec (2022-08-05)
  linux-4.9.y  f2fs: flush dirty meta pages when flushing them (2020-05-19)
  linux-3.18.y f2fs: use EINVAL for superblock with invalid magic (2019-07-30)

# tags:
$ git for-each-ref --sort=-creatordate refs/tags \
	--format='%(refname:short) %(subject) (%(creatordate:short))'
6.9-rc1-6.1  f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault (2024-03-14) tar.gz
6.9-rc1-6.6  f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault (2024-03-14) tar.gz
v6.8-rc3     Linux 6.8-rc3 (2024-02-04) tar.gz
v6.8-rc2     Linux 6.8-rc2 (2024-01-28) tar.gz
v6.8-rc1     Linux 6.8-rc1 (2024-01-21) tar.gz
6.8-rc1-6.1  f2fs: Avoid reading renamed directory if parent does not change (2024-01-12) tar.gz
6.8-rc1-6.6  f2fs: Avoid reading renamed directory if parent does not change (2024-01-12) tar.gz
f2fs-for-6.8-rc1 f2fs update for 6.8-rc1 (2024-01-11) tar.gz
v6.7         Linux 6.7 (2024-01-07) tar.gz
v6.7-rc8     Linux 6.7-rc8 (2023-12-31) tar.gz

# associated public inboxes:
# (number on the left is used for dev purposes)
    1212792 lkml
     380482 stable
     330431 netdev
     244405 linux-arm-kernel
     125598 linux-devicetree
     109776 linux-wireless
      97980 dri-devel
      70941 alsa-devel
      70762 linux-media
      69632 linuxppc-dev
      64929 linux-fsdevel
      59689 linux-mm
      51778 linux-patches
      50446 kvm
      50158 intel-gfx
      49920 linux-scsi
      45655 amd-gfx
      42503 linux-omap
      38287 linux-arch
      37373 linux-mips
      37311 linux-arm-msm
      31975 linux-xfs
      30473 linux-rdma
      29127 linux-nfs
      28921 linux-pm
      27048 linux-samsung-soc
      26699 linux-mediatek
      25962 linux-acpi
      25631 bpf
      25514 linux-crypto
      25237 netfilter-devel
      24914 linux-doc
      24349 linux-block
      24059 linux-s390
      22702 linux-mtd
      21406 linux-renesas-soc
      21298 linux-clk
      21233 linux-sh
      20694 linux-gpio
      20627 linux-pci
      20439 linux-tegra
      20222 linux-usb
      19874 linux-iio
      19534 linux-perf-users
      18650 kernel-janitors
      17491 linux-input
      16649 sparclinux
      16528 linux-btrfs
      16257 linux-riscv
      15720 linux-ide
      15304 xen-devel
      15231 linux-serial
      15151 linux-api
      14678 linux-ext4
      14590 u-boot
      14548 kvmarm
      14296 linux-fbdev
      14146 linux-mmc
      13996 driverdev-devel
      13942 linux-staging
      13579 linux-iommu
      13060 linux-kselftest
      12504 virtualization
      12418 linux-rockchip
      12231 linux-cifs
      12139 qemu-devel
      11799 linux-bluetooth
      11650 linux-kbuild
      11645 linux-spi
      10848 linux-amlogic
      10701 linux-i2c
      10639 linux-parisc
      10340 linux-ia64
       9922 linux-security-module
       9702 intel-wired-lan
       9528 platform-driver-x86
       9446 linux-f2fs-devel
       9176 ceph-devel
       9001 dm-devel
       8401 linux-um
       8178 linux-alpha
       7917 linux-m68k
       7506 linux-nvme
       7287 cgroups
       7249 linux-snps-arc
       7224 nvdimm
       7216 cluster-devel
       7124 nouveau
       6783 linux-can
       6625 lustre-devel
       6496 containers
       6476 linux-efi
       6308 linux-sunxi
       6290 batman
       6272 linux-watchdog
       6098 linux-rtc
       5953 kvm-ppc
       5808 linux-raid
       5527 linux-nvdimm
       5314 linux-rt-users
       5150 ocfs2-devel
       5146 linux-hwmon
       5118 dmaengine
       4965 linux-next
       4944 linux-hexagon
       4799 rcu
       4781 kernel-hardening
       4708 selinux
       4695 linux-leds
       4671 openrisc
       4588 linux-integrity
       4497 linux-hardening
       4483 linux-pwm
       4264 outreachy
       4217 linux-sctp
       4031 cip-dev
       3987 dpdk-dev
       3955 git
       3901 bridge
       3760 ath10k
       3748 lm-sensors
       3660 buildroot
       3651 io-uring
       3504 llvm
       3328 linux-remoteproc
       3319 mptcp
       3261 kexec
       3200 loongarch
       3139 linux-wpan
       3127 linux-hyperv
       3111 keyrings
       3103 linux-csky
       3076 soc
       2960 linux-nilfs
       2829 intel-xe
       2796 linux-bcache
       2776 target-devel
       2758 linux-phy
       2593 linux-fscrypt
       2466 ath11k
       2437 linux-trace-kernel
       2295 ath9k-devel
       2204 linux-erofs
       2180 lvs-devel
       2069 openembedded-core
       2010 linux-cxl
       2008 openbmc
       1998 linux-unionfs
       1947 linux-audit
       1893 linux-edac
       1860 linux-hams
       1591 cpufreq
       1553 phone-devel
       1523 chrome-platform
       1483 dccp
       1446 openembedded-devel
       1426 linux-trace-devel
       1419 reiserfs-devel
       1402 linux-fpga
       1372 b43-dev
       1296 linux-sound
       1280 linux-modules
       1258 historical-speck
       1180 asahi
       1129 v9fs
       1076 rust-for-linux
       1074 ntfs3
        959 linux-metag
        955 linux-kernel-mentees
        929 ntb
        874 fstests
        847 ecryptfs
        788 linux-x25
        773 ltp
        729 damon
        698 linux-spdx
        690 oe-kbuild-all
        684 netfilter
        654 ../../../../../../../igt-dev
        649 linux-man
        640 lvm-devel
        631 ath12k
        628 linux-sgx
        572 live-patching
        571 linux-i3c
        569 gfs2
        559 linux-coco
        540 autofs
        538 qemu-riscv
        537 tpmdd-devel
        524 cocci
        507 linux-ppp
        499 b4-sent
        488 linux-oxnas
        475 yocto
        466 linux-bcachefs
        411 oe-lkp
        395 virtio-dev
        368 linux-toolchains
        367 linux-sparse
        328 regressions
        311 linux-nfc
        311 oe-linux-nfc
        284 u-boot-amlogic
        283 wireguard
        262 lttng-dev
        261 mhi
        226 kernel-tls-handshake
        217 grub-devel
        211 imx
        209 yocto-meta-ti
        208 bitbake-devel
        207 mm-commits
        197 backports
        192 ofono
        189 acpica-devel
        174 yocto-meta-arago
        174 fsverity
        169 util-linux
        169 kernel-testers
        166 yocto-meta-freescale
        163 fio
        154 poky
        150 linux-embedded
        149 xdp-newbies
        149 xenomai
        149 kvm-ia64
        145 devicetree-compiler
        138 kernelci
        133 virtio-fs
        124 linux-kernel-announce
        111 audit
        107 yocto-meta-arm
         99 trinity
         90 linux-laptop
         88 workflows
         86 kernelnewbies
         86 iwd
         83 ../../../../../../../netfs
         80 yocto-meta-virtualization
         76 selinux-refpolicy
         72 linux-hotplug
         65 ksummit
         64 ksummit-discuss
         64 initramfs
         61 ../../../../../../../fuego
         60 yocto-docs
         58 perfbook
         57 linux-firmware
         57 ell
         57 yocto-toaster
         52 linux-btrace
         34 timestamp
         33 virtio-comment
         31 ../../../../../../../wireless-regdb
         29 linux-console
         27 ../../../../../../../powertop
         26 stable-rt
         25 linux-lvm
         22 devicetree-spec
         19 connman
         17 dash
         17 linux-safety
         16 linux-dash
         16 ultralinux
         13 hail-devel
         12 dwarves
         11 linux-debuggers
         10 linux-trace-users
         10 oe-kbuild
          9 radiotap
          9 kdevops
          8 kbd
          8 smatch
          7 ../../../../../../../brcm80211
          6 ccan
          6 ../../../../../../../tech-board-discuss
          5 linux-numa
          5 ../../../../../../../accel-config
          4 dm-crypt
          4 tools
          4 linux-msdos
          4 lartc
          3 stgt
          3 linux-smp
          2 linux-dwarves
          2 oe-chipsec
          2 linux-newbie
          1 signatures
          1 linux-config
          1 linux-8086
          1 mlmmj
          1 ../../../../../../../spdk

git clone