hwdb: drop boilerplate about match patterns being unstable

We've had this text since the beginning, but in fact the patterns must be
stable in order for people to create local hwdb entries. And we support that
and can't change the match patterns without being very careful. So let's just
drop the text.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2022-04-06 11:56:05 +02:00 committed by Yu Watanabe
parent cae7c28272
commit adbe000e3d
6 changed files with 0 additions and 29 deletions

View File

@ -3,11 +3,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 60-evdev.rules # 60-evdev.rules
# #
# Note: The format of the "evdev:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
#
# Match string formats: # Match string formats:
# evdev:<modalias> # evdev:<modalias>
# evdev:name:<device name>:dmi:<dmi string> # evdev:name:<device name>:dmi:<dmi string>

View File

@ -3,11 +3,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 60-input-id.rules # 60-input-id.rules
# #
# Note: The format of the "input-id:" prefix match key is a contract between
# the rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
#
# Match string formats: # Match string formats:
# id-input:modalias:<modalias> # id-input:modalias:<modalias>
# #

View File

@ -13,11 +13,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 60-evdev.rules # 60-evdev.rules
# #
# Note: The format of the "evdev:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
#
# Supported hardware matches are: # Supported hardware matches are:
# - Generic input devices match: # - Generic input devices match:
# evdev:input:bZZZZvYYYYpXXXXeWWWW-VVVV # evdev:input:bZZZZvYYYYpXXXXeWWWW-VVVV

View File

@ -3,11 +3,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 60-sensor.rules # 60-sensor.rules
# #
# Note: The format of the "sensor:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
#
# Match string formats: # Match string formats:
# sensor:modalias:<parent modalias pattern>:dmi:<dmi pattern> # sensor:modalias:<parent modalias pattern>:dmi:<dmi pattern>
# #

View File

@ -6,11 +6,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 70-mouse.rules # 70-mouse.rules
# #
# Note: The format of the "mouse:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
#
# Match key format: # Match key format:
# mouse:<subsystem>:v<vid>p<pid>:name:<name>: # mouse:<subsystem>:v<vid>p<pid>:name:<name>:
# #

View File

@ -7,10 +7,6 @@
# The lookup keys are composed in: # The lookup keys are composed in:
# 60-evdev.rules # 60-evdev.rules
# #
# Note: The format of the "evdev:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily a stable ABI.
#
# Supported hardware matches are: # Supported hardware matches are:
# - Generic input devices match: # - Generic input devices match:
# evdev:input:bZZZZvYYYYpXXXXeWWWW-VVVV # evdev:input:bZZZZvYYYYpXXXXeWWWW-VVVV