Skip to content

Commit

Permalink
release v4.11-1
Browse files Browse the repository at this point in the history
  • Loading branch information
raphael committed May 7, 2017
1 parent 890cf48 commit 50a1319
Show file tree
Hide file tree
Showing 12,268 changed files with 531,365 additions and 237,607 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
v4.11-1 2017-05-06
--------------------
Update to Linux 4.11

v4.10-9 2017-04-27
--------------------
Enable squashfs module
Expand Down
4 changes: 2 additions & 2 deletions aur/PKGBUILD
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Maintainer: Raphael Simon <[email protected]>

pkgbase=linux-samus4
pkgver=4.10
pkgrel=9
pkgver=4.11
pkgrel=1
arch=('x86_64')
url="https://github.com/raphael/linux-samus"
license=('GPL2')
Expand Down
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
23 changes: 23 additions & 0 deletions build/linux-4.11.0-ph+_4.11.0-ph+-18.dsc
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
Format: 3.0 (quilt)
Source: linux-4.11.0-ph+
Binary: linux-image-4.11.0-ph+, linux-headers-4.11.0-ph+, linux-firmware-image-4.11.0-ph+, linux-libc-dev
Architecture: any all
Version: 4.11.0-ph+-18
Maintainer: Anonymous <root@chromia>
Homepage: http://www.kernel.org/
Standards-Version: 3.8.4
Build-Depends: bc, kmod, cpio
Package-List:
linux-firmware-image-4.11.0-ph+ deb kernel optional arch=all
linux-headers-4.11.0-ph+ deb kernel optional arch=any
linux-image-4.11.0-ph+ deb kernel optional arch=any
linux-libc-dev deb devel optional arch=any
Checksums-Sha1:
f5c1bcbf11908c20e63ccd8bb5716ea9eafb0607 307865565 linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
ffddaa738b7c93663f597b2ea0fe85a46ec1ac5a 1282 linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
Checksums-Sha256:
d89329574efd068c90793d6e88fbd945d141160d3ad235416b3b5671627c1ece 307865565 linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
fd5fcf131f5deef1407c97e34f912ba03b891de66dcb93d3d328c244cd0c7d75 1282 linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
Files:
34c196ec53af995944dc86eeabd639cb 307865565 linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
4b919d040efc9319e18fc62c6ad12378 1282 linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
43 changes: 43 additions & 0 deletions build/linux-4.11.0-ph+_4.11.0-ph+-18_amd64.changes
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
Format: 1.8
Date: Sat, 06 May 2017 17:44:24 -0700
Source: linux-4.11.0-ph+
Binary: linux-image-4.11.0-ph+ linux-headers-4.11.0-ph+ linux-firmware-image-4.11.0-ph+ linux-libc-dev
Architecture: source amd64 all
Version: 4.11.0-ph+-18
Distribution: vivid
Urgency: low
Maintainer: Anonymous <root@chromia>
Changed-By: Anonymous <root@chromia>
Description:
linux-firmware-image-4.11.0-ph+ - Linux kernel firmware, version 4.11.0-ph+
linux-headers-4.11.0-ph+ - Linux kernel headers for 4.11.0-ph+ on ${kernel:debarch}
linux-image-4.11.0-ph+ - Linux kernel, version 4.11.0-ph+
linux-libc-dev - Linux support headers for userspace development
Changes:
linux-4.11.0-ph+ (4.11.0-ph+-18) vivid; urgency=low
.
* Custom built Linux kernel.
Checksums-Sha1:
a7455cbe3b315ec9e80951fcd7823e4600c405a2 1174 linux-4.11.0-ph+_4.11.0-ph+-18.dsc
f5c1bcbf11908c20e63ccd8bb5716ea9eafb0607 307865565 linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
ffddaa738b7c93663f597b2ea0fe85a46ec1ac5a 1282 linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
c95b7e23f169622897f7a6dee412136705114c1a 736194 linux-firmware-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
27303a00576001e8e56681ede7e2222cea914ed4 10637984 linux-headers-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
c4d9135159974b5bad163624ab5d491815443d58 18502444 linux-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
6009f413a76d79ce1014a546dcfea0bb908e8b5d 905182 linux-libc-dev_4.11.0-ph+-18_amd64.deb
Checksums-Sha256:
f95cb52027ed24bbc6628d56bb5caf4eaae76bf7b70e0d4fd0785722af05b703 1174 linux-4.11.0-ph+_4.11.0-ph+-18.dsc
d89329574efd068c90793d6e88fbd945d141160d3ad235416b3b5671627c1ece 307865565 linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
fd5fcf131f5deef1407c97e34f912ba03b891de66dcb93d3d328c244cd0c7d75 1282 linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
113d25ecad822fd366638fcc9388aa0bf0e0ef9cbe46268eb6a36f7e4ec1027e 736194 linux-firmware-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
6f5612c876d7baf632119c31c829de843ff2da52f3b7fff1401f79d9a8762f10 10637984 linux-headers-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
f4c67100082fb965d2ee18df54ab096148033326e82bc567caa0a33ca1ccd973 18502444 linux-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
baf7f6712d50488a0e6d9092aa862c38e0bd4bdbe1b323b1059bc018f72d8bf8 905182 linux-libc-dev_4.11.0-ph+-18_amd64.deb
Files:
b15db1077a9f19b2a559f42f99a8b63c 1174 kernel optional linux-4.11.0-ph+_4.11.0-ph+-18.dsc
34c196ec53af995944dc86eeabd639cb 307865565 kernel optional linux-4.11.0-ph+_4.11.0-ph+.orig.tar.gz
4b919d040efc9319e18fc62c6ad12378 1282 kernel optional linux-4.11.0-ph+_4.11.0-ph+-18.debian.tar.gz
3c8c6e58a38d97db409a082fd2320257 736194 kernel optional linux-firmware-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
7b131b103a0be6d37611e1982adbc26e 10637984 kernel optional linux-headers-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
dcac8afc62fa063641a306b416545cd5 18502444 kernel optional linux-image-4.11.0-ph+_4.11.0-ph+-18_amd64.deb
b0537c8e75f3e94ec3673a42fcb050b1 905182 devel optional linux-libc-dev_4.11.0-ph+-18_amd64.deb
3 changes: 3 additions & 0 deletions build/linux/.mailmap
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,8 @@ Linas Vepstas <[email protected]>
Linus Lüssing <[email protected]> <[email protected]>
Linus Lüssing <[email protected]> <[email protected]>
Mark Brown <[email protected]>
Martin Kepplinger <[email protected]> <[email protected]>
Martin Kepplinger <[email protected]> <[email protected]>
Matthieu CASTET <[email protected]>
Mauro Carvalho Chehab <[email protected]> <[email protected]>
Mauro Carvalho Chehab <[email protected]> <[email protected]>
Expand Down Expand Up @@ -171,6 +173,7 @@ Vlad Dogaru <[email protected]> <[email protected]>
Vladimir Davydov <[email protected]> <[email protected]>
Vladimir Davydov <[email protected]> <[email protected]>
Takashi YOSHII <[email protected]>
Yakir Yang <[email protected]> <[email protected]>
Yusuke Goda <[email protected]>
Gustavo Padovan <[email protected]>
Gustavo Padovan <[email protected]>
4 changes: 2 additions & 2 deletions build/linux/Documentation/00-INDEX
Original file line number Diff line number Diff line change
Expand Up @@ -270,8 +270,8 @@ m68k/
- directory with info about Linux on Motorola 68k architecture.
mailbox.txt
- How to write drivers for the common mailbox framework (IPC).
md-cluster.txt
- info on shared-device RAID MD cluster.
md/
- directory with info about Linux Software RAID
media/
- info on media drivers: uAPI, kAPI and driver documentation.
memory-barriers.txt
Expand Down
119 changes: 0 additions & 119 deletions build/linux/Documentation/ABI/obsolete/sysfs-block-zram

This file was deleted.

8 changes: 8 additions & 0 deletions build/linux/Documentation/ABI/testing/configfs-rdma_cm
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,11 @@ Description: RDMA-CM based connections from HCA <hca> at port <port-num>
will be initiated with this RoCE type as default.
The possible RoCE types are either "IB/RoCE v1" or "RoCE v2".
This parameter has RW access.

What: /config/rdma_cm/<hca>/ports/<port-num>/default_roce_tos
Date: February 7, 2017
KernelVersion: 4.11.0
Description: RDMA-CM QPs from HCA <hca> at port <port-num>
will be created with this TOS as default.
This can be overridden by using the rdma_set_option API.
The possible RoCE TOS values are 0-255.
101 changes: 8 additions & 93 deletions build/linux/Documentation/ABI/testing/sysfs-block-zram
Original file line number Diff line number Diff line change
Expand Up @@ -22,41 +22,6 @@ Description:
device. The reset operation frees all the memory associated
with this device.

What: /sys/block/zram<id>/num_reads
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The num_reads file is read-only and specifies the number of
reads (failed or successful) done on this device.

What: /sys/block/zram<id>/num_writes
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The num_writes file is read-only and specifies the number of
writes (failed or successful) done on this device.

What: /sys/block/zram<id>/invalid_io
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The invalid_io file is read-only and specifies the number of
non-page-size-aligned I/O requests issued to this device.

What: /sys/block/zram<id>/failed_reads
Date: February 2014
Contact: Sergey Senozhatsky <[email protected]>
Description:
The failed_reads file is read-only and specifies the number of
failed reads happened on this device.

What: /sys/block/zram<id>/failed_writes
Date: February 2014
Contact: Sergey Senozhatsky <[email protected]>
Description:
The failed_writes file is read-only and specifies the number of
failed writes happened on this device.

What: /sys/block/zram<id>/max_comp_streams
Date: February 2014
Contact: Sergey Senozhatsky <[email protected]>
Expand All @@ -73,74 +38,24 @@ Description:
available and selected compression algorithms, change
compression algorithm selection.

What: /sys/block/zram<id>/notify_free
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The notify_free file is read-only. Depending on device usage
scenario it may account a) the number of pages freed because
of swap slot free notifications or b) the number of pages freed
because of REQ_DISCARD requests sent by bio. The former ones
are sent to a swap block device when a swap slot is freed, which
implies that this disk is being used as a swap disk. The latter
ones are sent by filesystem mounted with discard option,
whenever some data blocks are getting discarded.

What: /sys/block/zram<id>/zero_pages
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The zero_pages file is read-only and specifies number of zero
filled pages written to this disk. No memory is allocated for
such pages.

What: /sys/block/zram<id>/orig_data_size
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The orig_data_size file is read-only and specifies uncompressed
size of data stored in this disk. This excludes zero-filled
pages (zero_pages) since no memory is allocated for them.
Unit: bytes

What: /sys/block/zram<id>/compr_data_size
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The compr_data_size file is read-only and specifies compressed
size of data stored in this disk. So, compression ratio can be
calculated using orig_data_size and this statistic.
Unit: bytes

What: /sys/block/zram<id>/mem_used_total
Date: August 2010
Contact: Nitin Gupta <[email protected]>
Description:
The mem_used_total file is read-only and specifies the amount
of memory, including allocator fragmentation and metadata
overhead, allocated for this disk. So, allocator space
efficiency can be calculated using compr_data_size and this
statistic.
Unit: bytes

What: /sys/block/zram<id>/mem_used_max
Date: August 2014
Contact: Minchan Kim <[email protected]>
Description:
The mem_used_max file is read/write and specifies the amount
of maximum memory zram have consumed to store compressed data.
For resetting the value, you should write "0". Otherwise,
you could see -EINVAL.
The mem_used_max file is write-only and is used to reset
the counter of maximum memory zram have consumed to store
compressed data. For resetting the value, you should write
"0". Otherwise, you could see -EINVAL.
Unit: bytes

What: /sys/block/zram<id>/mem_limit
Date: August 2014
Contact: Minchan Kim <[email protected]>
Description:
The mem_limit file is read/write and specifies the maximum
amount of memory ZRAM can use to store the compressed data. The
limit could be changed in run time and "0" means disable the
limit. No limit is the initial state. Unit: bytes
The mem_limit file is write-only and specifies the maximum
amount of memory ZRAM can use to store the compressed data.
The limit could be changed in run time and "0" means disable
the limit. No limit is the initial state. Unit: bytes

What: /sys/block/zram<id>/compact
Date: August 2015
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
What: /sys/bus/i2c/devices/.../trickle_charge_bypass
Date: Jan 2017
KernelVersion: 4.11
Contact: Enric Balletbo i Serra <[email protected]>
Description: Attribute for enable/disable the trickle charge bypass
The trickle_charge_bypass attribute allows the userspace to
enable/disable the Trickle charge FET bypass.
Loading

0 comments on commit 50a1319

Please sign in to comment.