From: Rafael J. Wysocki
Fix kerneldoc comments of __device_suspend_noirq(),
__device_suspend_late() and __device_suspend() where the function
names in kerneldoc don't match the actual names of the functions.
Signed-off-by: Rafael J. Wysocki
On Wed, 11 Oct 2017, Roman Gushchin wrote:
> > But let's move the discussion forward to fix it. To avoid necessarily
> > accounting memory to the root mem cgroup, have we considered if it is even
> > necessary to address the root mem cgroup? For the users who opt-in to
> > this heuristic,
On Thu, Oct 12, 2017 at 10:24 PM, Tom Saeger wrote:
> Signed-off-by: Tom Saeger
> ---
> Documentation/power/interface.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/power/interface.txt
>
> On Oct 12, 2017, at 7:44 AM, Khalid Aziz wrote:
>
> Hi Anthony,
>
> Please quote only the relevant parts of the patch with comments. That makes
> it much easier to find the comments.
Okay.
>
> On 10/06/2017 04:12 PM, Anthony Yznaga wrote:
>>> On Sep 25, 2017, at
Signed-off-by: Tom Saeger
---
Documentation/ABI/obsolete/sysfs-gpio | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/obsolete/sysfs-gpio
b/Documentation/ABI/obsolete/sysfs-gpio
index 867c1fab20e2..32513dc2eec9 100644
---
Signed-off-by: Tom Saeger
---
.../RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html
Signed-off-by: Tom Saeger
---
Documentation/process/4.Coding.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/4.Coding.rst
b/Documentation/process/4.Coding.rst
index 6df19943dd4d..26b106071364 100644
---
Signed-off-by: Tom Saeger
---
Documentation/locking/rt-mutex-design.txt | 2 +-
Documentation/pi-futex.txt| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/rt-mutex-design.txt
Make refs to selftests files valid including:
- watchdog-test.c
- dnotify_test.c
Signed-off-by: Tom Saeger
---
Documentation/filesystems/dnotify.txt| 2 +-
Documentation/watchdog/hpwdt.txt | 2 +-
Documentation/watchdog/pcwd-watchdog.txt | 2 +-
3 files
Signed-off-by: Tom Saeger
---
Documentation/trace/intel_th.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/intel_th.txt b/Documentation/trace/intel_th.txt
index f92070e7dde0..7a57165c2492 100644
---
Signed-off-by: Tom Saeger
---
Documentation/power/interface.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/interface.txt
b/Documentation/power/interface.txt
index 7dc75f48e8bd..27df7f98668a 100644
---
Signed-off-by: Tom Saeger
---
Documentation/doc-guide/kernel-doc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/doc-guide/kernel-doc.rst
b/Documentation/doc-guide/kernel-doc.rst
index b24854b5d6be..0268335414ce 100644
---
Batch (2) set of simple document ref fixes.
Tom Saeger (8):
Documentation: fix locking rt-mutex doc refs
Documentation: fix ref to sphinx/kerneldoc.py
Documentation: fix ref to workqueue content
Documentation: fix ref to coccinelle content
Documentation: fix ref to trace stm content
On Thu, Oct 12, 2017 at 05:24:25PM +, Jonathan Corbet wrote:
> On Tue, 10 Oct 2017 12:35:58 -0500
> Tom Saeger wrote:
>
> > Recently, while reading up on binfmt I attempted to open a document ref
> > only to find it was invalid. I did a quick grep, found all the
> >
On Thu, 12 Oct 2017 15:00:06 +1100 (AEDT)
Finn Thain wrote:
> CONFIG_BLK_DEV_HD_IDE was removed in commit 80aa31cb460d ("ide:
> remove CONFIG_BLK_DEV_HD_IDE config option (take 2)") but the ide-cd
> documentation was not updated and still asks users to disable it,
On Tue, 10 Oct 2017 12:35:58 -0500
Tom Saeger wrote:
> Recently, while reading up on binfmt I attempted to open a document ref
> only to find it was invalid. I did a quick grep, found all the
> binfmt_misc related broken refs and sent a patch.
>
> Fine. Easy.
>
> Then I
On Mon, 9 Oct 2017 18:26:15 +0300
Jani Nikula wrote:
> Add a simple script and build target to do a treewide grep for
> references to files under Documentation, and report the non-existing
> file in stderr. It tries to take into account punctuation not part of
> the
On 10/12/2017 11:02 AM, Jonathan Corbet wrote:
> On Mon, 2 Oct 2017 17:44:17 -0600
> Shuah Khan wrote:
>
>> Update to include details on make O=dir support and other changes improve
>> test results output.
>
> So the three patches you sent me appear to be a part of a
Hi Anthony,
Please quote only the relevant parts of the patch with comments. That
makes it much easier to find the comments.
On 10/06/2017 04:12 PM, Anthony Yznaga wrote:
On Sep 25, 2017, at 9:49 AM, Khalid Aziz wrote:
This patch extends mprotect to enable ADI
On 10/12/2017 03:55 PM, Guenter Roeck wrote:
On 10/12/2017 06:00 AM, Maciej Purski wrote:
On 10/12/2017 02:39 PM, Krzysztof Kozlowski wrote:
On Thu, Oct 12, 2017 at 2:36 PM, Maciej Purski wrote:
Add optional max expected current property which allows calibrating
the
On 10/12/2017 06:00 AM, Maciej Purski wrote:
On 10/12/2017 02:39 PM, Krzysztof Kozlowski wrote:
On Thu, Oct 12, 2017 at 2:36 PM, Maciej Purski wrote:
Add optional max expected current property which allows calibrating
the ina sensor in order to achieve requested
On 10/12/2017 03:18 PM, Maciej Purski wrote:
> diff --git a/Documentation/devicetree/bindings/hwmon/ina2xx.txt
> b/Documentation/devicetree/bindings/hwmon/ina2xx.txt
> index 02af0d9..9268595 100644
> --- a/Documentation/devicetree/bindings/hwmon/ina2xx.txt
> +++
Max expected current is used for calculating calibration register value,
Current LSB and Power LSB according to equations found in ina datasheet:
current_lsb = max_expected_current / 2^15
calibration_register = 0.00512 / (current_lsb * r_shunt)
power_lsb = 25 * current_lsb (for ina231, 230, 226)
Max expected current is used for calculating calibration register value,
Current LSB and Power LSB according to equations found in ina datasheet:
current_lsb = max_expected_current / 2^15
calibration_register = 0.00512 / (current_lsb * r_shunt)
power_lsb = 25 * current_lsb (for ina231, 230, 226)
Add optional max expected current property which allows calibrating
the ina sensor in order to achieve requested measure scale. Document
the changes in Documentation/hwmon/ina2xx.
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/hwmon/ina2xx.txt | 4 +++-
Set max expected current to values required by the documentation,
in order to achieve desired precision.
Signed-off-by: Maciej Purski
---
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 4
1 file changed, 4 insertions(+)
diff --git
Hi all,
this patchset makes it possible to calibrate ina2xx drivers with different
calibration values, which are calculated using max expected current value.
It can be read from device tree, platform data or changed during run-time
using sysfs. If it isn't specified in device tree or platform
On 10/12/2017 02:39 PM, Krzysztof Kozlowski wrote:
On Thu, Oct 12, 2017 at 2:36 PM, Maciej Purski wrote:
Add optional max expected current property which allows calibrating
the ina sensor in order to achieve requested measure scale. Document
the changes in
On Thu, Oct 12, 2017 at 2:36 PM, Maciej Purski wrote:
> Add optional max expected current property which allows calibrating
> the ina sensor in order to achieve requested measure scale. Document
> the changes in Documentation/hwmon/ina2xx.
>
> Signed-off-by: Maciej Purski
Max expected current is used for calculating calibration register value,
Current LSB and Power LSB according to equations found in ina datasheet:
current_lsb = max_expected_current / 2^15
calibration_register = 0.00512 / (current_lsb * r_shunt)
power_lsb = 25 * current_lsb (for ina231, 230, 226)
Add optional max expected current property which allows calibrating
the ina sensor in order to achieve requested measure scale. Document
the changes in Documentation/hwmon/ina2xx.
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/hwmon/ina2xx.txt | 4 +++-
Max expected current is used for calculating calibration register value,
Current LSB and Power LSB according to equations found in ina datasheet:
current_lsb = max_expected_current / 2^15
calibration_register = 0.00512 / (current_lsb * r_shunt)
power_lsb = 25 * current_lsb (for ina231, 230, 226)
Hi all,
this patchset makes it possible to calibrate ina2xx drivers with different
calibration values, which are calculated using max expected current value.
It can be read from device tree, platform data or changed during run-time
using sysfs. If it isn't specified in device tree or platform
On Wed 11-10-17 13:27:44, David Rientjes wrote:
> On Wed, 11 Oct 2017, Michal Hocko wrote:
>
> > > For these reasons: unfair comparison of root mem cgroup usage to bias
> > > against that mem cgroup from oom kill in system oom conditions, the
> > > ability of users to completely evade the oom
From: Wei-Ning Huang
The current hid-multitouch driver only allow the report of two
orientations, vertical and horizontal. We use the Azimuth orientation
usage 0x3F under the Digitizer usage page to report orientation if the
device supports it.
Changelog:
v1 -> v2:
-
35 matches
Mail list logo