From: Jonathan Cameron <jic23@kernel.org>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: lars@metafoo.de, peress@chromium.org,
enric.balletbo@collabora.com, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/3] Documentation: ABI: iio: Use What: consistently
Date: Sun, 6 Sep 2020 16:24:07 +0100 [thread overview]
Message-ID: <20200906162407.2173a5d6@archlinux> (raw)
In-Reply-To: <20200901030017.3221295-2-gwendal@chromium.org>
On Mon, 31 Aug 2020 20:00:15 -0700
Gwendal Grignou <gwendal@chromium.org> wrote:
> Change "[w|W]hat[:| ]" to What: for consistency.
>
> Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
> ---
> No changes since v1
Already applied from v1
Jonathan
> Documentation/ABI/testing/sysfs-bus-iio | 48 ++++++++++++-------------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index c3767d4d01a6f..47df16c87862d 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -401,21 +401,21 @@ Description:
> Hardware applied calibration offset (assumed to fix production
> inaccuracies).
>
> -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
> -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
> -what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
> -what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
> +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
> What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale
> What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale
> What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale
> @@ -483,7 +483,7 @@ Description:
> If a discrete set of scale values is available, they
> are listed in this attribute.
>
> -What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
> What: /sys/bus/iio/devices/iio:deviceX/in_intensity_red_hardwaregain
> What: /sys/bus/iio/devices/iio:deviceX/in_intensity_green_hardwaregain
> What: /sys/bus/iio/devices/iio:deviceX/in_intensity_blue_hardwaregain
> @@ -750,9 +750,9 @@ What: /sys/.../events/in_voltageY_raw_thresh_falling_value
> What: /sys/.../events/in_tempY_raw_thresh_rising_value
> What: /sys/.../events/in_tempY_raw_thresh_falling_value
> What: /sys/.../events/in_illuminance0_thresh_falling_value
> -what: /sys/.../events/in_illuminance0_thresh_rising_value
> -what: /sys/.../events/in_proximity0_thresh_falling_value
> -what: /sys/.../events/in_proximity0_thresh_rising_value
> +What: /sys/.../events/in_illuminance0_thresh_rising_value
> +What: /sys/.../events/in_proximity0_thresh_falling_value
> +What: /sys/.../events/in_proximity0_thresh_rising_value
> KernelVersion: 2.6.37
> Contact: linux-iio@vger.kernel.org
> Description:
> @@ -830,11 +830,11 @@ What: /sys/.../events/in_tempY_thresh_rising_hysteresis
> What: /sys/.../events/in_tempY_thresh_falling_hysteresis
> What: /sys/.../events/in_tempY_thresh_either_hysteresis
> What: /sys/.../events/in_illuminance0_thresh_falling_hysteresis
> -what: /sys/.../events/in_illuminance0_thresh_rising_hysteresis
> -what: /sys/.../events/in_illuminance0_thresh_either_hysteresis
> -what: /sys/.../events/in_proximity0_thresh_falling_hysteresis
> -what: /sys/.../events/in_proximity0_thresh_rising_hysteresis
> -what: /sys/.../events/in_proximity0_thresh_either_hysteresis
> +What: /sys/.../events/in_illuminance0_thresh_rising_hysteresis
> +What: /sys/.../events/in_illuminance0_thresh_either_hysteresis
> +What: /sys/.../events/in_proximity0_thresh_falling_hysteresis
> +What: /sys/.../events/in_proximity0_thresh_rising_hysteresis
> +What: /sys/.../events/in_proximity0_thresh_either_hysteresis
> KernelVersion: 3.13
> Contact: linux-iio@vger.kernel.org
> Description:
next prev parent reply other threads:[~2020-09-06 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 3:00 [PATCH v2 0/3] docs: abi: iio: RFC: Request to add event when offsets calculated by sensorhub change Gwendal Grignou
2020-09-01 3:00 ` [PATCH v2 1/3] Documentation: ABI: iio: Use What: consistently Gwendal Grignou
2020-09-06 15:24 ` Jonathan Cameron [this message]
2020-09-01 3:00 ` [PATCH v2 2/3] Documentation: ABI: iio: Add offsets for some sensors Gwendal Grignou
2020-09-06 15:38 ` Jonathan Cameron
2020-09-01 3:00 ` [PATCH v2 3/3] Documentation: ABI: iio: Add event when offset/scale changes Gwendal Grignou
2020-09-06 15:31 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200906162407.2173a5d6@archlinux \
--to=jic23@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@chromium.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=peress@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.