Re: [PATCH] selftests/bpf: tcpbpf_kern: use in6_* macros from glibc

On 02/21/2018 10:51 AM, Anders Roxell wrote: > Both glibc and the kernel have in6_* macros definitions. Build fails > because it picks up wrong in6_* macro from the kernel header and not the > header from glibc. > > Fixes build error below: > clang -I. -I./include/uapi -I../../../include/uapi >

Re: [PATCH] selftests/bpf: tcpbpf_kern: use in6_* macros from glibc

On 02/21/2018 10:51 AM, Anders Roxell wrote: > Both glibc and the kernel have in6_* macros definitions. Build fails > because it picks up wrong in6_* macro from the kernel header and not the > header from glibc. > > Fixes build error below: > clang -I. -I./include/uapi -I../../../include/uapi >

[PATCH] m68k: time: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- arch/m68k/kernel/time.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] m68k: time: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- arch/m68k/kernel/time.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] selftests/bpf: update gitignore with test_libbpf_open

On 02/21/2018 03:30 PM, Anders Roxell wrote: > bpf builds a test program for loading BPF ELF files. Add the executable > to the .gitignore list. > > Signed-off-by: Anders Roxell Tested-by: Daniel Díaz > --- >

Re: [PATCH] selftests/bpf: update gitignore with test_libbpf_open

On 02/21/2018 03:30 PM, Anders Roxell wrote: > bpf builds a test program for loading BPF ELF files. Add the executable > to the .gitignore list. > > Signed-off-by: Anders Roxell Tested-by: Daniel Díaz > --- > tools/testing/selftests/bpf/.gitignore | 1 + > 1 file changed, 1 insertion(+) > >

Re: [RFC PATCH v16 0/6] mm: security: ro protection for dynamic data

On Wed, Feb 21, 2018 at 11:56:22AM +0200, Igor Stoppa wrote: > On 21/02/18 03:36, Dave Chinner wrote: > > On Tue, Feb 20, 2018 at 03:56:00PM -0800, Matthew Wilcox wrote: > >> On Wed, Feb 21, 2018 at 08:36:04AM +1100, Dave Chinner wrote: > >>> FWIW, I'm not wanting to use it to replace static

Re: [RFC PATCH v16 0/6] mm: security: ro protection for dynamic data

On Wed, Feb 21, 2018 at 11:56:22AM +0200, Igor Stoppa wrote: > On 21/02/18 03:36, Dave Chinner wrote: > > On Tue, Feb 20, 2018 at 03:56:00PM -0800, Matthew Wilcox wrote: > >> On Wed, Feb 21, 2018 at 08:36:04AM +1100, Dave Chinner wrote: > >>> FWIW, I'm not wanting to use it to replace static

[PATCH] alpha: rtc: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- arch/alpha/kernel/rtc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] alpha: rtc: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- arch/alpha/kernel/rtc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Digital Signage Expo - DSE

Hi, I understand your company is exhibiting in Digital Signage Expo on MAR 27-30-2018. Would you be interested in the complete contact information with email addresses of Decision-Makers and Buyers In these Categories: * Ad Agencies/Brand Marketers * Architects *

Digital Signage Expo - DSE

Hi, I understand your company is exhibiting in Digital Signage Expo on MAR 27-30-2018. Would you be interested in the complete contact information with email addresses of Decision-Makers and Buyers In these Categories: * Ad Agencies/Brand Marketers * Architects *

[PATCH] tools/gpio/gpio-event-mon: fix warning

PRIu64 is defined in user space to match libc's uint64_t definition. However, gpioevent_data structure in the kernel is defined using the kernel's own __u64 type. gpio-event-mon.c: In function ‘monitor_device’: gpio-event-mon.c:102:19: warning: format ‘%lu’ expects argument of type ‘long

[PATCH] tools/gpio/gpio-event-mon: fix warning

PRIu64 is defined in user space to match libc's uint64_t definition. However, gpioevent_data structure in the kernel is defined using the kernel's own __u64 type. gpio-event-mon.c: In function ‘monitor_device’: gpio-event-mon.c:102:19: warning: format ‘%lu’ expects argument of type ‘long

Re: [PATCH v2] iio:dummy: Replace S_IWUSR by 0200

On Wed, 21 Feb 2018, Rodrigo Siqueira wrote: > This patch fixes the checkpatch.pl warning: > > drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions > 'S_IWUSR' are not preferred. Consider using octal permissions '0200'. I haven't studied up on it in great detail, but isn't

Re: [PATCH v2] proc: fix /proc/*/map_files lookup some more

On Wed, 21 Feb 2018 22:53:40 +0300 Alexey Dobriyan wrote: > I totally forgot that _parse_integer() accepts arbitrary amount of > leading zeroes leading to the following: > > OK > # readlink /proc/1/map_files/56427ecba000-56427eddc000 >

Re: [PATCH v2] proc: fix /proc/*/map_files lookup some more

On Wed, 21 Feb 2018 22:53:40 +0300 Alexey Dobriyan wrote: > I totally forgot that _parse_integer() accepts arbitrary amount of > leading zeroes leading to the following: > > OK > # readlink /proc/1/map_files/56427ecba000-56427eddc000 > /lib/systemd/systemd > >

Re: [PATCH v2] iio:dummy: Replace S_IWUSR by 0200

On Wed, 21 Feb 2018, Rodrigo Siqueira wrote: > This patch fixes the checkpatch.pl warning: > > drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions > 'S_IWUSR' are not preferred. Consider using octal permissions '0200'. I haven't studied up on it in great detail, but isn't

[PATCH] selftests/bpf: update gitignore with test_libbpf_open

bpf builds a test program for loading BPF ELF files. Add the executable to the .gitignore list. Signed-off-by: Anders Roxell --- tools/testing/selftests/bpf/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/bpf/.gitignore

[PATCH] selftests/bpf: update gitignore with test_libbpf_open

bpf builds a test program for loading BPF ELF files. Add the executable to the .gitignore list. Signed-off-by: Anders Roxell --- tools/testing/selftests/bpf/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/bpf/.gitignore

Re: [PATCH v2 7/8] [PATCH 7/8] drivers/hwmon: Add a generic PECI hwmon client driver

Hi Guenter, Thanks for sharing your time to review this code. Please check my answers inline. On 2/21/2018 10:26 AM, Guenter Roeck wrote: On Wed, Feb 21, 2018 at 08:16:05AM -0800, Jae Hyun Yoo wrote: This commit adds a generic PECI hwmon client driver implementation. Signed-off-by: Jae

Re: [PATCH v2 7/8] [PATCH 7/8] drivers/hwmon: Add a generic PECI hwmon client driver

Hi Guenter, Thanks for sharing your time to review this code. Please check my answers inline. On 2/21/2018 10:26 AM, Guenter Roeck wrote: On Wed, Feb 21, 2018 at 08:16:05AM -0800, Jae Hyun Yoo wrote: This commit adds a generic PECI hwmon client driver implementation. Signed-off-by: Jae

[PATCH 000/100] rtc: remove cargo culted code

Hello, This series: - removes useless calls to rtc_valid_tm in .read_time, .set_time and .set_alarm - removes code setting default values for RTCs (and lets the core handle it) - removes useless "time is invalid" messages at probe time - removes useless indirect calls Those were mostly

[PATCH 000/100] rtc: remove cargo culted code

Hello, This series: - removes useless calls to rtc_valid_tm in .read_time, .set_time and .set_alarm - removes code setting default values for RTCs (and lets the core handle it) - removes useless "time is invalid" messages at probe time - removes useless indirect calls Those were mostly

[PATCH 004/100] rtc: rs5c348: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni ---

[PATCH 004/100] rtc: rs5c348: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rs5c348.c | 5 - 1 file

[PATCH 003/100] rtc: cmos: let the core handle invalid time

Setting the rtc to a valid time when the time is invalid is a bad practice, because then userspace doesn't know it shouldn't trust the RTC. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-cmos.c | 12 1 file changed, 12 deletions(-) diff --git

[PATCH 003/100] rtc: cmos: let the core handle invalid time

Setting the rtc to a valid time when the time is invalid is a bad practice, because then userspace doesn't know it shouldn't trust the RTC. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-cmos.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/rtc/rtc-cmos.c

[PATCH 002/100] rtc: ds1553: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni ---

[PATCH 002/100] rtc: ds1553: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1553.c | 4 1 file

[PATCH 007/100] rtc: ab3100: stop validating rtc_time in .read_time

rtc_time64_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab3100.c | 2 +- 1 file changed, 1

[PATCH 007/100] rtc: ab3100: stop validating rtc_time in .read_time

rtc_time64_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab3100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 008/100] rtc: ab8500: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab8500.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 006/100] rtc: ab-b5ze-s3: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab-b5ze-s3.c | 4 +--- 1 file changed, 1 insertion(+), 3

[PATCH 008/100] rtc: ab8500: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab8500.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 006/100] rtc: ab-b5ze-s3: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ab-b5ze-s3.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH 009/100] rtc: ac100: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ac100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 009/100] rtc: ac100: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ac100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 012/100] rtc: coh901331: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 2 +- 1 file changed, 1

[PATCH 014/100] rtc: da9052: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9052.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 010/100] rtc: au1xxx: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-au1xxx.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 016/100] rtc: da9063: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9063.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 012/100] rtc: coh901331: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 014/100] rtc: da9052: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9052.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 010/100] rtc: au1xxx: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-au1xxx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 016/100] rtc: da9063: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9063.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 005/100] rtc: stk17ta8: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni ---

[PATCH 005/100] rtc: stk17ta8: let the core handle invalid time

Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-stk17ta8.c | 4 1 file

[PATCH 011/100] rtc: bq32k: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-bq32k.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 011/100] rtc: bq32k: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-bq32k.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 013/100] rtc: cpcap: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-cpcap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 013/100] rtc: cpcap: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-cpcap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 015/100] rtc: da9055: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9055.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 015/100] rtc: da9055: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-da9055.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 018/100] rtc: ds1286: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1286.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 018/100] rtc: ds1286: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1286.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 021/100] rtc: ds1307: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1307.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 021/100] rtc: ds1307: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1307.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 019/100] rtc: ds1302: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1302.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 019/100] rtc: ds1302: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1302.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 017/100] rtc: ds1216: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1216.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 017/100] rtc: ds1216: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1216.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 020/100] rtc: ds1305: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1305.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 020/100] rtc: ds1305: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1305.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 022/100] rtc: ds1343: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1343.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 022/100] rtc: ds1343: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1343.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 030/100] rtc: fm3130: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-fm3130.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 030/100] rtc: fm3130: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-fm3130.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 031/100] rtc: jz4740: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 031/100] rtc: jz4740: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 024/100] rtc: ds1390: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1390.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 024/100] rtc: ds1390: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1390.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 027/100] rtc: ds2404: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds2404.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 025/100] rtc: ds1685: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1685.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 027/100] rtc: ds2404: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds2404.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 025/100] rtc: ds1685: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1685.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 4.15 000/163] 4.15.5-stable review

On 02/21/2018 05:47 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.5 release. > There are 163 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.15 000/163] 4.15.5-stable review

On 02/21/2018 05:47 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.5 release. > There are 163 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH 033/100] rtc: lpc32xx: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-lpc32xx.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 037/100] rtc: m48t59: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m48t59.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 033/100] rtc: lpc32xx: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-lpc32xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 037/100] rtc: m48t59: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m48t59.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 034/100] rtc: ls1x: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ls1x.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 034/100] rtc: ls1x: stop validating rtc_time in .read_time

rtc_time_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ls1x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 032/100] rtc: lpc24xx: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-lpc24xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 032/100] rtc: lpc24xx: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-lpc24xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 028/100] rtc: ds3232: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds3232.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 028/100] rtc: ds3232: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds3232.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 036/100] rtc: m48t35: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m48t35.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 036/100] rtc: m48t35: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m48t35.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 023/100] rtc: ds1347: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1347.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 035/100] rtc: m41t94: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m41t94.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 023/100] rtc: ds1347: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1347.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 035/100] rtc: m41t94: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m41t94.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 026/100] rtc: ds1742: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1742.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 026/100] rtc: ds1742: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-ds1742.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 051/100] rtc: pcap: stop validating rtc_time in .read_time

rtc_time64_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcap.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 051/100] rtc: pcap: stop validating rtc_time in .read_time

rtc_time64_to_tm never generates an invalid tm. It is not necessary to validate it. Also, the RTC core is always calling rtc_valid_tm after the read_time callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 047/100] rtc: msm6242: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-msm6242.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 047/100] rtc: msm6242: stop validating rtc_time in .read_time

The RTC core is always calling rtc_valid_tm after the read_time callback. It is not necessary to call it just before returning from the callback. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-msm6242.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

<    3   4   5   6   7   8   9   10   11   12   >