[vimrc]: cscope: implement cnext/cprev shortcuts

.circleci/config.yml

@@ -0,0 +1,80 @@
+version: 2
+general:
+ artifacts:
+
+jobs:
+ build:
+ docker:
+ - image: lktp/publish:0.2
+ environment:
+ [email protected]:linux-kernel-labs/linux-kernel-labs.github.io.git
+ steps:
+ - restore_cache:
+ key: code-tree-shallow
+ - run:
+ name: checkout
+ command: |
+ set -x
+ mkdir -p ~/.ssh/
+ ssh-keyscan -H github.com >> ~/.ssh/known_hosts
+ git config --global user.email "[email protected]"
+ git config --global user.name "Circle CI"
+ if ! [ -d linux ]; then
+ git clone --depth=1 $CIRCLE_REPOSITORY_URL;
+ fi
+ if cd linux; then
+ if [[ $CIRCLE_BRANCH == pull/* ]]; then
+ git fetch --depth=1 origin $CIRCLE_BRANCH/head;
+ else
+ git fetch --depth=1 origin $CIRCLE_BRANCH;
+ fi
+ git reset --hard $CIRCLE_SHA1
+ cd ..
+ fi
+ if ! [ -d linux-kernel-labs.github.io ]; then
+ git clone --depth=1 $GITHUB_IO
+ fi
+ if cd linux-kernel-labs.github.io; then
+ git fetch --depth=1 origin master
+ git reset --hard origin/master
+ cd ..
+ fi
+ - save_cache:
+ key: code-tree-shallow-{{ epoch }}
+ paths:
+ - /home/ubuntu/project/linux/.git
+ - /home/ubuntu/project/linux-kernel-labs.github.io/.git
+ - run:
+ name: build
+ command: |
+ rm -rf linux/Documentation/output
+ cd linux/tools/labs && make docs
+ - add_ssh_keys:
+ fingerprints:
+ "8e:db:3c:ef:d0:4e:84:9f:78:46:e9:2f:1a:1e:32:81"
+ - run:
+ name: publish
+ command: |
+ set -x
+ if cd linux-kernel-labs.github.io; then
+ rm -rf $CIRCLE_BRANCH
+ mkdir -p $CIRCLE_BRANCH
+ cp -r ../linux/Documentation/output/teaching/* $CIRCLE_BRANCH/
+ git add $CIRCLE_BRANCH/
+ git commit --allow-empty -m "Publish $CIRCLE_BRANCH (built from ${CIRCLE_PULL_REQUEST:-$CIRCLE_BRANCH})"
+ git push
+ export GITHUB_SHA=$CIRCLE_SHA1
+ export GITHUB_USER=linux-kernel-labs
+ export GITHUB_REPO=$CIRCLE_PROJECT_REPONAME
+ export GITHUB_CONTEXT="ci/circleci: publish"
+ export GITHUB_TARGET_URL="http://linux-kernel-labs.github.io/$CIRCLE_BRANCH"
+ export GITHUB_DESCRIPTION="published at $GITHUB_TARGET_URL"
+ github-status-reporter --state success --debug
+ cd ..
+ fi
+
+workflows:
+ version: 2
+ build:
+ jobs:
+ - build

.github/workflows/main.yml

@@ -0,0 +1,40 @@
+on:
+ push:
+ branches:
+ - master
+ pull_request:
+ branches:
+ - master
+
+jobs:
+ build_job:
+ runs-on: ubuntu-20.04
+ name: Build documentation
+ steps:
+ - name: Checkout
+ uses: actions/checkout@v2
+ - name: Install native dependencies
+ run: sudo apt-get update -y && sudo apt-get install -y ditaa graphviz
+ - name: Install pip dependencies
+ run: sudo pip install Sphinx==1.6.7 sphinx_rtd_theme==1.3.0 hieroglyph==1.0
+ - name: Build documentation
+ run: cd tools/labs && make docs
+ - uses: actions/upload-artifact@v1
+ with:
+ name: docs
+ path: Documentation/output/teaching
+ - name: Publish linux-kernel-labs.gihub.io
+ env:
+ URL: https://api.github.com/repos/linux-kernel-labs/linux-kernel-labs.github.io/dispatches
+ HASH: yxg-obg:q8qqs27s1617p99n2p131s71n827npn1on4445q3 
+ run: |
+ curl -X POST -u $(tr a-zA-Z n-za-mN-ZA-M <<<"$HASH") --header 'content-type: application/json' $URL \
+ --data '{"event_type" : "publish", "client_payload" : { "run_id" : "${{ github.run_id }}", "dir" : "${{ github.ref }}" } }'
+ - name: Comment on PR
+ if: github.event_name == 'pull_request'
+ env:
+ URL: ${{ github.event.pull_request.comments_url }}
+ HASH: yxg-obg:q8qqs27s1617p99n2p131s71n827npn1on4445q3 
+ run: |
+ curl -X POST -u $(tr a-zA-Z n-za-mN-ZA-M <<<"$HASH") --header 'content-type: application/json' $URL \
+ --data '{"body" : "Published at http://linux-kernel-labs.github.io/${{ github.ref }}"}'

Documentation/ABI/testing/sysfs-class-devlink

@@ -5,8 +5,8 @@ Description:
  Provide a place in sysfs for the device link objects in the
  kernel at any given time. The name of a device link directory,
  denoted as ... above, is of the form <supplier>--<consumer>
- where <supplier> is the supplier device name and <consumer> is
- the consumer device name.
+ where <supplier> is the supplier bus:device name and <consumer>
+ is the consumer bus:device name.
 
 What: /sys/class/devlink/.../auto_remove_on
 Date: May 2020

Documentation/ABI/testing/sysfs-devices-consumer

@@ -4,5 +4,6 @@ Contact: Saravana Kannan <[email protected]>
 Description:
  The /sys/devices/.../consumer:<consumer> are symlinks to device
  links where this device is the supplier. <consumer> denotes the
- name of the consumer in that device link. There can be zero or
- more of these symlinks for a given device.
+ name of the consumer in that device link and is of the form
+ bus:device name. There can be zero or more of these symlinks
+ for a given device.

Documentation/ABI/testing/sysfs-devices-supplier

@@ -4,5 +4,6 @@ Contact: Saravana Kannan <[email protected]>
 Description:
  The /sys/devices/.../supplier:<supplier> are symlinks to device
  links where this device is the consumer. <supplier> denotes the
- name of the supplier in that device link. There can be zero or
- more of these symlinks for a given device.
+ name of the supplier in that device link and is of the form
+ bus:device name. There can be zero or more of these symlinks
+ for a given device.

Documentation/Makefile

@@ -90,6 +90,9 @@ htmldocs:
  @$(srctree)/scripts/sphinx-pre-install --version-check
  @+$(foreach var,$(SPHINXDIRS),$(call loop_cmd,sphinx,html,$(var),,$(var)))
 
+slides:
+ @+$(foreach var,$(SPHINXDIRS),$(call loop_cmd,sphinx,slides,$(var),,$(var)))
+
 linkcheckdocs:
  @$(foreach var,$(SPHINXDIRS),$(call loop_cmd,sphinx,linkcheck,$(var),,$(var)))
 

Documentation/admin-guide/device-mapper/dm-integrity.rst

@@ -177,14 +177,20 @@ bitmap_flush_interval:number
  The bitmap flush interval in milliseconds. The metadata buffers
  are synchronized when this interval expires.
 
+allow_discards
+ Allow block discard requests (a.k.a. TRIM) for the integrity device.
+ Discards are only allowed to devices using internal hash.
+
 fix_padding
  Use a smaller padding of the tag area that is more
  space-efficient. If this option is not present, large padding is
  used - that is for compatibility with older kernels.
 
-allow_discards
- Allow block discard requests (a.k.a. TRIM) for the integrity device.
- Discards are only allowed to devices using internal hash.
+legacy_recalculate
+ Allow recalculating of volumes with HMAC keys. This is disabled by
+ default for security reasons - an attacker could modify the volume,
+ set recalc_sector to zero, and the kernel would not detect the
+ modification.
 
 The journal mode (D/J), buffer_sectors, journal_watermark, commit_time and
 allow_discards can be changed when reloading the target (load an inactive

Documentation/admin-guide/kernel-parameters.txt

@@ -5663,6 +5663,7 @@
  device);
  j = NO_REPORT_LUNS (don't use report luns
  command, uas only);
+ k = NO_SAME (do not use WRITE_SAME, uas only)
  l = NOT_LOCKABLE (don't try to lock and
  unlock ejectable media, not on uas);
  m = MAX_SECTORS_64 (don't transfer more
@@ -5964,6 +5965,10 @@
  This option is obsoleted by the "nopv" option, which
  has equivalent effect for XEN platform.
 
+ xen_no_vector_callback
+ [KNL,X86,XEN] Disable the vector callback for Xen
+ event channel interrupts.
+
  xen_scrub_pages= [XEN]
  Boolean option to control scrubbing pages before giving them back
  to Xen, for use by other domains. Can be also changed at runtime

Documentation/asm-annotations.rst

@@ -100,6 +100,11 @@ Instruction Macros
 ~~~~~~~~~~~~~~~~~~
 This section covers ``SYM_FUNC_*`` and ``SYM_CODE_*`` enumerated above.
 
+``objtool`` requires that all code must be contained in an ELF symbol. Symbol
+names that have a ``.L`` prefix do not emit symbol table entries. ``.L``
+prefixed symbols can be used within a code region, but should be avoided for
+denoting a range of code via ``SYM_*_START/END`` annotations.
+
 * ``SYM_FUNC_START`` and ``SYM_FUNC_START_LOCAL`` are supposed to be **the
  most frequent markings**. They are used for functions with standard calling
  conventions -- global and local. Like in C, they both align the functions to

Documentation/conf.py

@@ -15,6 +15,9 @@
 import sys
 import os
 import sphinx
+import subprocess
+
+from distutils.version import LooseVersion
 
 from subprocess import check_output
 
@@ -123,6 +126,16 @@
 else:
  extensions.append("sphinx.ext.pngmath")
 
+try:
+ hglyph_ver = subprocess.check_output(["hieroglyph", "--version"]).decode('utf-8')
+ if LooseVersion(hglyph_ver) > LooseVersion("1.0.0"):
+ extensions.append("hieroglyph")
+except:
+ None
+
+extensions.append("ditaa")
+extensions.append("asciicast")
+
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']
 
@@ -264,11 +277,9 @@
 
 html_static_path = ['sphinx-static']
 
-html_context = {
- 'css_files': [
- '_static/theme_overrides.css',
- ],
-}
+def setup(app):
+ app.add_stylesheet('theme_overrides.css')
+
 
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied

Documentation/devicetree/bindings/display/bridge/sii902x.txt

@@ -8,6 +8,8 @@ Optional properties:
  - interrupts: describe the interrupt line used to inform the host
  about hotplug events.
  - reset-gpios: OF device-tree gpio specification for RST_N pin.
+ - iovcc-supply: I/O Supply Voltage (1.8V or 3.3V)
+ - cvcc12-supply: Digital Core Supply Voltage (1.2V)
 
  HDMI audio properties:
  - #sound-dai-cells: <0> or <1>. <0> if only i2s or spdif pin
@@ -54,6 +56,8 @@ Example:
  compatible = "sil,sii9022";
  reg = <0x39>;
  reset-gpios = <&pioA 1 0>;
+ iovcc-supply = <&v3v3_hdmi>;
+ cvcc12-supply = <&v1v2_hdmi>;
 
  #sound-dai-cells = <0>;
  sil,i2s-data-lanes = < 0 1 2 >;

Documentation/devicetree/bindings/net/renesas,etheravb.yaml

@@ -163,6 +163,7 @@ allOf:
  enum:
  - renesas,etheravb-r8a774a1
  - renesas,etheravb-r8a774b1
+ - renesas,etheravb-r8a774e1
  - renesas,etheravb-r8a7795
  - renesas,etheravb-r8a7796
  - renesas,etheravb-r8a77961

Documentation/devicetree/bindings/rtc/rtc.yaml

@@ -63,6 +63,11 @@ properties:
  description:
  Enables wake up of host system on alarm.
 
+ reset-source:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ The RTC is able to reset the machine.
+
 additionalProperties: true
 
 ...

Documentation/gpu/todo.rst

@@ -273,6 +273,24 @@ Contact: Daniel Vetter, Noralf Tronnes
 
 Level: Advanced
 
+Garbage collect fbdev scrolling acceleration
+--------------------------------------------
+
+Scroll acceleration is disabled in fbcon by hard-wiring p->scrollmode =
+SCROLL_REDRAW. There's a ton of code this will allow us to remove:
+- lots of code in fbcon.c
+- a bunch of the hooks in fbcon_ops, maybe the remaining hooks could be called
+ directly instead of the function table (with a switch on p->rotate)
+- fb_copyarea is unused after this, and can be deleted from all drivers
+
+Note that not all acceleration code can be deleted, since clearing and cursor
+support is still accelerated, which might be good candidates for further
+deletion projects.
+
+Contact: Daniel Vetter
+
+Level: Intermediate
+
 idr_init_base()
 ---------------
 

Documentation/locking/seqlock.rst

@@ -89,7 +89,7 @@ Read path::
 
 .. _seqcount_locktype_t:
 
-Sequence counters with associated locks (``seqcount_LOCKTYPE_t``)
+Sequence counters with associated locks (``seqcount_LOCKNAME_t``)
 -----------------------------------------------------------------
 
 As discussed at :ref:`seqcount_t`, sequence count write side critical
@@ -115,27 +115,26 @@ The following sequence counters with associated locks are defined:
  - ``seqcount_mutex_t``
  - ``seqcount_ww_mutex_t``
 
-The plain seqcount read and write APIs branch out to the specific
-seqcount_LOCKTYPE_t implementation at compile-time. This avoids kernel
-API explosion per each new seqcount LOCKTYPE.
+The sequence counter read and write APIs can take either a plain
+seqcount_t or any of the seqcount_LOCKNAME_t variants above.
 
-Initialization (replace "LOCKTYPE" with one of the supported locks)::
+Initialization (replace "LOCKNAME" with one of the supported locks)::
 
  /* dynamic */
- seqcount_LOCKTYPE_t foo_seqcount;
- seqcount_LOCKTYPE_init(&foo_seqcount, &lock);
+ seqcount_LOCKNAME_t foo_seqcount;
+ seqcount_LOCKNAME_init(&foo_seqcount, &lock);
 
  /* static */
- static seqcount_LOCKTYPE_t foo_seqcount =
- SEQCNT_LOCKTYPE_ZERO(foo_seqcount, &lock);
+ static seqcount_LOCKNAME_t foo_seqcount =
+ SEQCNT_LOCKNAME_ZERO(foo_seqcount, &lock);
 
  /* C99 struct init */
  struct {
- .seq = SEQCNT_LOCKTYPE_ZERO(foo.seq, &lock),
+ .seq = SEQCNT_LOCKNAME_ZERO(foo.seq, &lock),
  } foo;
 
 Write path: same as in :ref:`seqcount_t`, while running from a context
-with the associated LOCKTYPE lock acquired.
+with the associated write serialization lock acquired.
 
 Read path: same as in :ref:`seqcount_t`.