$ git log --pretty=format:'%h %s (%cs)%d'
592fe8980688e Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2012-04-17)
(HEAD -> master)
d44c6d4fa9b3d Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2012-04-17)
bc0cf58ec7ccd Merge git://git.samba.org/sfrench/cifs-2.6 (2012-04-17)
4643b05662966 Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2012-04-16)
cdd5983063cad Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2012-04-16)
a6cb9ee7cabe6 PCI: Retry BARs restoration for Type 0 headers only (2012-04-16)
5191d566c0230 Documentation: maintainer change (2012-04-16)
c76f39bddb84f ia64: fix futex_atomic_cmpxchg_inatomic() (2012-04-16)
57f73c2c89a5d ext4: fix handling of journalled quota options (2012-04-16)
c06a9ebdb7a4f checkpatch: revert --strict test for net/ and drivers/net block comment style (2012-04-16)
...
$ git cat-file blob HEAD:README
Linux kernel release 3.x <http://kernel.org/>
These are the release notes for Linux version 3. 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 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 (eg. your home directory) and
unpack it:
gzip -cd linux-3.X.tar.gz | tar xvf -
or
bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
Replace "XX" 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 3.x releases by patching. Patches are
distributed in the traditional gzip and the newer bzip2 format. To
install by patching, get all the newer patch files, enter the
top level directory of the kernel source (linux-3.x) and execute:
gzip -cd ../patch-3.x.gz | patch -p1
or
bzip2 -dc ../patch-3.x.bz2 | patch -p1
(repeat xx for all versions bigger than the version of your current
source tree, _in_order_) and you should be ok. You may want to remove
the backup files (xxx~ or xxx.orig), and make sure that there are no
failed patches (xxx# or xxx.rej). If there are, either you or me has
made a mistake.
Unlike patches for the 3.x kernels, patches for the 3.x.y kernels
(also known as the -stable kernels) are not incremental but instead apply
directly to the base 3.x kernel. Please read
Documentation/applying-patches.txt for more information.
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.
- If you are upgrading between releases using the stable series patches
(for example, patch-3.x.y), note that these "dot-releases" are
not incremental and must be applied to the 3.x base tree. For
example, if your base kernel is 3.0 and you want to apply the
3.0.3 patch, you do not and indeed must not first apply the
3.0.1 and 3.0.2 patches. Similarly, if you are running kernel
version 3.0.2 and want to jump to 3.0.3, you must first
reverse the 3.0.2 patch (that is, patch -R) _before_ applying
the 3.0.3 patch.
You can read more on this in Documentation/applying-patches.txt
- 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 3.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" allow you to specify an alternate
place for the output files (including .config).
Example:
kernel source code: /usr/src/linux-3.N
build directory: /home/name/build/kernel
To configure and build the kernel use:
cd /usr/src/linux-3.N
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.
- Alternate 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" X windows (Qt) based configuration tool.
"make gconfig" X windows (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 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.
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 inserting
"V=1" in 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 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/ .
Alternately 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.
- Alternately, 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))'
* master Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2012-04-17)
v3.3-hpc Linux 3.3 (2012-03-18)
v2.6.36-hpc update onfig-hp7xx-flashrom to include EABI since we are using that userland. (2011-12-10)
v2.6.34-hpc ARM: Nec MobilePro900/c: Fix to isp116x-hcd driver (2011-12-10)
v2.6.29-hpc Seems like it infact only got 640x480x2 bytes so the size is probably correct. So reset it to the mp900/c standard. We want to see it boot before we fiddle to much. (2011-12-10)
v2.6.26-hpc / : Apply previous jlime v2.6.26-stable patch * This patch makes HP Jornada 700-series and Mobilepro 900/c buildable/workable. Both are without 100% hardware support but usable. * HP Jornada 600-series is workable but without hd64461 support. There is an mfd driver (development) inside but it isn't working yet. HP Jornada 600-series users should (for now) instead use the v2.6.17-hpc branch. * Im applying it all as one giant patch to avoid to create too much git-history at once. It will most likely require some minor cleanups in the future. (2011-12-10)
v2.6.24-hpc Make maui config abit smaller so its easier to bugtrack (2011-12-10)
v2.6.19-hpc drivers/ide/legacy/ide-cs.c: Add support for Sandisk SDP cards (2011-12-10)
v2.6.17-hpc config-hp6xx-2.6.17 : Add PCMCIA SCSI drivers * seems like some people actually have this hardware so lets support it. (2011-12-09)
v2.6.37-hpc This patch fixes some compilation issues, due to lock/unlock_console not being implemented yet (and not worth the hassle to fix) and also reverting the drm_pci_init/drm_pci_exit. (2011-03-05)
# tags:
$ git for-each-ref --sort=-creatordate refs/tags \
--format='%(refname:short) %(subject) (%(creatordate:short))'
v3.2-rc4 Linux 3.2-rc4 (2011-12-01) tar.gz
v3.2-rc3 Linux 3.2-rc3 (2011-11-23) tar.gz
v3.2-rc2 Linux 3.2-rc2 (2011-11-15) tar.gz
v3.2-rc1 Linux 3.2-rc1 (2011-11-07) tar.gz
v3.1 Linux v3.1 (2011-10-24) tar.gz
v3.1-rc10 Linux 3.1-rc10 (2011-10-17) tar.gz
v3.1-rc9 Linux 3.1-rc9 (2011-10-04) tar.gz
v3.1-rc8 Linux 3.1-rc8 (2011-09-27) tar.gz
v3.1-rc7 Linux 3.1-rc7 (2011-09-21) tar.gz
v3.1-rc6 Linux 3.1-rc6 (2011-09-12) tar.gz
...
# associated public inboxes:
# (number on the left is used for dev purposes)
1244613 ../../../../../../../lkml
391513 stable
338235 netdev
250786 linux-arm-kernel
130065 linux-devicetree
111767 linux-wireless
100644 dri-devel
72497 alsa-devel
72016 linux-media
71730 linuxppc-dev
67356 linux-fsdevel
63199 linux-mm
57437 linux-patches
51903 kvm
51753 intel-gfx
50690 linux-scsi
48379 amd-gfx
42731 linux-omap
39818 linux-arch
39234 linux-arm-msm
38688 linux-mips
34095 linux-xfs
31052 linux-rdma
29858 linux-nfs
29833 linux-pm
28216 bpf
27582 linux-mediatek
27508 linux-samsung-soc
26420 linux-doc
26403 linux-crypto
26387 linux-acpi
25577 netfilter-devel
25316 linux-block
25131 linux-s390
22938 linux-mtd
22141 linux-renesas-soc
21913 linux-sh
21883 linux-clk
21568 linux-gpio
21225 linux-pci
20994 linux-usb
20946 linux-tegra
20924 linux-perf-users
20542 linux-iio
19118 kernel-janitors
18592 linux-riscv
18047 linux-input
17571 sparclinux
17188 linux-btrfs
15892 linux-ide
15636 linux-serial
15385 kvmarm
15383 xen-devel
15226 linux-api
14994 linux-ext4
14835 linux-kselftest
14708 u-boot
14588 linux-staging
14566 linux-fbdev
14433 linux-mmc
14408 linux-iommu
13996 driverdev-devel
13029 linux-rockchip
12929 virtualization
12724 linux-cifs
12192 qemu-devel
12190 linux-kbuild
12095 linux-bluetooth
11868 linux-spi
11429 linux-parisc
11051 linux-amlogic
11046 linux-i2c
10466 intel-wired-lan
10446 linux-security-module
10341 linux-ia64
10041 platform-driver-x86
9867 linux-f2fs-devel
9462 dm-devel
9371 ceph-devel
9041 linux-um
8691 linux-alpha
8437 linux-m68k
7845 linux-snps-arc
7771 cgroups
7733 linux-nvme
7283 nvdimm
7228 nouveau
7216 cluster-devel
6821 linux-can
6756 linux-sunxi
6625 lustre-devel
6587 linux-efi
6496 containers
6471 linux-watchdog
6297 batman
6253 linux-rtc
5954 kvm-ppc
5890 linux-raid
5588 linux-hwmon
5527 linux-nvdimm
5464 linux-hexagon
5424 linux-rt-users
5345 dmaengine
5314 ocfs2-devel
5210 openrisc
5057 rcu
5021 selinux
5014 linux-next
4909 linux-hardening
4859 linux-leds
4833 linux-integrity
4781 kernel-hardening
4600 linux-pwm
4509 loongarch
4504 intel-xe
4286 cip-dev
4285 linux-sctp
4281 outreachy
4206 io-uring
4000 dpdk-dev
4000 llvm
3994 bridge
3968 git
3948 ath10k
3914 linux-trace-kernel
3878 linux-csky
3847 mptcp
3827 linux-sound
3748 lm-sensors
3685 buildroot
3463 linux-remoteproc
3371 linux-hyperv
3353 linux-wpan
3353 kexec
3296 keyrings
3145 soc
3033 linux-nilfs
2988 linux-phy
2897 linux-bcache
2779 target-devel
2692 ath11k
2633 linux-fscrypt
2599 linux-erofs
2326 linux-cxl
2295 ath9k-devel
2236 lvs-devel
2110 linux-edac
2088 linux-modules
2086 openembedded-core
2071 openbmc
2054 linux-unionfs
1968 linux-hams
1947 linux-audit
1617 phone-devel
1593 chrome-platform
1591 cpufreq
1532 dccp
1483 linux-fpga
1481 linux-trace-devel
1460 openembedded-devel
1421 reiserfs-devel
1377 asahi
1374 b43-dev
1367 v9fs
1359 rust-for-linux
1258 historical-speck
1168 ath12k
1117 ntfs3
970 linux-kernel-mentees
970 ntb
959 linux-metag
925 linux-bcachefs
892 imx
888 fstests
878 ecryptfs
838 linux-x25
831 damon
822 gfs2
779 ltp
764 b4-sent
729 oe-kbuild-all
713 linux-spdx
694 linux-sgx
684 netfilter
674 igt-dev
663 linux-man
653 linux-coco
640 lvm-devel
599 live-patching
591 linux-i3c
587 fsverity
545 qemu-riscv
541 autofs
537 tpmdd-devel
527 linux-ppp
525 cocci
488 linux-oxnas
477 yocto
421 linux-toolchains
418 oe-lkp
408 regressions
399 virtio-dev
369 linux-sparse
317 netfs
311 linux-nfc
311 oe-linux-nfc
310 mhi
293 wireguard
288 u-boot-amlogic
262 lttng-dev
253 acpica-devel
244 audit
227 kernel-tls-handshake
218 grub-devel
210 bitbake-devel
210 yocto-meta-ti
209 mm-commits
198 backports
193 ofono
176 yocto-meta-arago
173 brcm80211
170 util-linux
169 kernel-testers
166 yocto-meta-freescale
164 fio
154 poky
150 xenomai
150 linux-embedded
149 xdp-newbies
149 kvm-ia64
145 devicetree-compiler
140 kernelci
136 workflows
133 virtio-fs
124 linux-kernel-announce
115 yocto-meta-arm
99 trinity
97 ../../../../../../../linux-aspeed
96 iwd
90 linux-laptop
86 kernelnewbies
83 yocto-meta-virtualization
76 selinux-refpolicy
72 linux-hotplug
65 ksummit
64 ksummit-discuss
64 initramfs
61 fuego
60 yocto-docs
59 linux-firmware
59 perfbook
57 ell
57 yocto-toaster
52 linux-btrace
40 ../../../../../../../linux-rt-devel
35 timestamp
33 virtio-comment
31 wireless-regdb
29 stable-rt
29 linux-console
27 powertop
25 linux-lvm
22 devicetree-spec
19 connman
18 dash
17 linux-safety
16 linux-dash
16 ultralinux
13 hail-devel
12 dwarves
12 oe-kbuild
12 lkmm
11 linux-debuggers
11 ../../../../../../../barebox
10 linux-trace-users
10 kdevops
9 radiotap
9 kbd
9 arm-scmi
8 smatch
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
2 dtrace
2 yocto-patches
1 signatures
1 linux-bugs
1 linux-config
1 linux-8086
1 mlmmj
1 spdk
git clone https://yhbt.net/lore/pub/scm/linux/kernel/git/kristoffer/linux-hpc.git