Re: [PATCH v3] spi: master driver to enable RTC on ICPDAS LP-8841

On Mon, Feb 22, 2016 at 02:57:42PM +0300, Sergei Ianovich wrote: Please don't send new patches in the middle of old threads, it makes it hard to find what the current versions of things are. >v2..v3 to fix Mark Brown review comments >* drop dependencies in Kconfig No, what I was asking

Re: [PATCH v3] spi: master driver to enable RTC on ICPDAS LP-8841

On Mon, Feb 22, 2016 at 02:57:42PM +0300, Sergei Ianovich wrote: Please don't send new patches in the middle of old threads, it makes it hard to find what the current versions of things are. >v2..v3 to fix Mark Brown review comments >* drop dependencies in Kconfig No, what I was asking

[PATCH 0/4] sched: Display deadline bandwidth and other SCHED_DEBUG clean up

[ Nothing different since my v2 I posted, except hopefully people will look at it this time :-) I also removed the RFC ] I'm starting to play with SCHED_DEADLINE a bit and I'm able to cause a bandwidth "leak". Then I realized there's no way to examine what bandwidths are enabled on which CPUs.

[PATCH 1/4] sched: Move sched_feature file setup into debug.c

From: "Steven Rostedt (Red Hat)" As sched_feature is only created when SCHED_DEBUG is enabled, and the file debug.c is only compiled when SCHED_DEBUG is enabled, it makes sense to move sched_feature setup into that file and get rid of the #ifdef. Signed-off-by: Steven

[PATCH 0/4] sched: Display deadline bandwidth and other SCHED_DEBUG clean up

[ Nothing different since my v2 I posted, except hopefully people will look at it this time :-) I also removed the RFC ] I'm starting to play with SCHED_DEADLINE a bit and I'm able to cause a bandwidth "leak". Then I realized there's no way to examine what bandwidths are enabled on which CPUs.

[PATCH 1/4] sched: Move sched_feature file setup into debug.c

From: "Steven Rostedt (Red Hat)" As sched_feature is only created when SCHED_DEBUG is enabled, and the file debug.c is only compiled when SCHED_DEBUG is enabled, it makes sense to move sched_feature setup into that file and get rid of the #ifdef. Signed-off-by: Steven Rostedt ---

[PATCH 2/4] sched: Move sched_domain_sysctl to debug.c

From: "Steven Rostedt (Red Hat)" The sched_domain_sysctl setup is only enabled when SCHED_DEBUG is configured. As debug.c is only compiled when SCHED_DEBUG is configured as well, move the setup of sched_domain_sysctl into that file. Note, the

[PATCH 3/4] sched: Add bandwidth ratio to /proc/sched_debug

From: "Steven Rostedt (Red Hat)" Playing with SCHED_DEADLINE and cpusets, I found that I was unable to create new SCHED_DEADLINE tasks, with the error of EBUSY as if the bandwidth was already used up. I then realized there wa no way to see what bandwidth is used by the

[PATCH 2/4] sched: Move sched_domain_sysctl to debug.c

From: "Steven Rostedt (Red Hat)" The sched_domain_sysctl setup is only enabled when SCHED_DEBUG is configured. As debug.c is only compiled when SCHED_DEBUG is configured as well, move the setup of sched_domain_sysctl into that file. Note, the (un)register_sched_domain_sysctl() functions had to

[PATCH 3/4] sched: Add bandwidth ratio to /proc/sched_debug

From: "Steven Rostedt (Red Hat)" Playing with SCHED_DEADLINE and cpusets, I found that I was unable to create new SCHED_DEADLINE tasks, with the error of EBUSY as if the bandwidth was already used up. I then realized there wa no way to see what bandwidth is used by the runqueues to debug the

[PATCH 4/4] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers

From: "Steven Rostedt (Red Hat)" To have nanosecond output displayed in a more human readable format, its nicer to convert it to a seconds format (XXX.Y). The problem is that to do so, the numbers must be divided by NSEC_PER_SEC, and moded too. But as these numbers

[PATCH 4/4] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers

From: "Steven Rostedt (Red Hat)" To have nanosecond output displayed in a more human readable format, its nicer to convert it to a seconds format (XXX.Y). The problem is that to do so, the numbers must be divided by NSEC_PER_SEC, and moded too. But as these numbers are 64 bit, this can

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

On Mon, Feb 22, 2016 at 10:32 AM, Juri Lelli wrote: > On 19/02/16 23:14, Rafael J. Wysocki wrote: >> On Friday, February 19, 2016 08:09:17 AM Juri Lelli wrote: >> > Hi Rafael, >> > >> > On 18/02/16 21:22, Rafael J. Wysocki wrote: >> > > On Mon, Feb 15, 2016 at 10:47 PM, Rafael

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

On Mon, Feb 22, 2016 at 10:32 AM, Juri Lelli wrote: > On 19/02/16 23:14, Rafael J. Wysocki wrote: >> On Friday, February 19, 2016 08:09:17 AM Juri Lelli wrote: >> > Hi Rafael, >> > >> > On 18/02/16 21:22, Rafael J. Wysocki wrote: >> > > On Mon, Feb 15, 2016 at 10:47 PM, Rafael J. Wysocki >> > >

Re: [PATCH v3 00/12] pwm: add support for atomic update

On Mon, Feb 22, 2016 at 11:15:09AM -0800, Doug Anderson wrote: > Note that historically I remember that Linus Torvalds has stated that > there is no stable API within the Linux kernel and that forcing the > in-kernel API to never change was bad for software development. I > tracked down my

Re: [PATCH v3 00/12] pwm: add support for atomic update

On Mon, Feb 22, 2016 at 11:15:09AM -0800, Doug Anderson wrote: > Note that historically I remember that Linus Torvalds has stated that > there is no stable API within the Linux kernel and that forcing the > in-kernel API to never change was bad for software development. I > tracked down my

[PATCH v2] sscanf: implement basic character sets

linux-next-20160222. v2: - Use kstrndup() to copy the character set from fmt instead of using a statically allocated array lib/vsprintf.c | 39 +++ 1 file changed, 39 insertions(+) diff --git a/lib/vsprintf.c b/lib/vsprintf.c index 525c8e1..93a6f52

[PATCH v2] sscanf: implement basic character sets

in (or not in) the set. This implementation differs from its glibc counterpart in that it does not support character ranges (e.g., 'a-z' or '0-9'), the hyphen '-' is *not* a special character, and the brackets themselves cannot be matched. Signed-off-by: Jessica Yu --- Patch based on linux-next-20160222. v2

Re: [GIT PULL] remaining tpmdd fixes for Linux 4.5

On Mon, Feb 22, 2016 at 12:11:48PM -0700, Jason Gunthorpe wrote: > On Mon, Feb 22, 2016 at 09:08:28PM +0200, Jarkko Sakkinen wrote: > > On Mon, Feb 22, 2016 at 10:52:45AM -0700, Jason Gunthorpe wrote: > > > On Mon, Feb 22, 2016 at 04:50:23PM +0200, Jarkko Sakkinen wrote: > > > > > > > I already

Re: [GIT PULL] remaining tpmdd fixes for Linux 4.5

On Mon, Feb 22, 2016 at 12:11:48PM -0700, Jason Gunthorpe wrote: > On Mon, Feb 22, 2016 at 09:08:28PM +0200, Jarkko Sakkinen wrote: > > On Mon, Feb 22, 2016 at 10:52:45AM -0700, Jason Gunthorpe wrote: > > > On Mon, Feb 22, 2016 at 04:50:23PM +0200, Jarkko Sakkinen wrote: > > > > > > > I already

Re: [PATCH v3 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

On Fri, Feb 19, 2016 at 08:01:17PM -0600, John Dahlstrom wrote: > On Fri, 19 Feb 2016, Darren Hart wrote: > > >See stable_kernel_rules.txt for how to specify relevant versions. I'm curious > >why there is a gap from 3.18 to 4.1. > > > >What you probably meant was: > > > >Cc:

Re: [PATCH v3 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

On Fri, Feb 19, 2016 at 08:01:17PM -0600, John Dahlstrom wrote: > On Fri, 19 Feb 2016, Darren Hart wrote: > > >See stable_kernel_rules.txt for how to specify relevant versions. I'm curious > >why there is a gap from 3.18 to 4.1. > > > >What you probably meant was: > > > >Cc: # 3.18.x > > > >If

Re: [PATCH v5 1/4] media: pxa_camera: fix the buffer free path

Guennadi Liakhovetski writes: > On Sun, 21 Feb 2016, Robert Jarzmik wrote: > Please, have a look at > http://git.linuxtv.org/gliakhovetski/v4l-dvb.git/log/?h=for-4.6-2 > If all is good there, no need for a v6 Thanks for fixing the *_dma_irq() mess, and sorry for that.

Re: [PATCH v5 1/4] media: pxa_camera: fix the buffer free path

Guennadi Liakhovetski writes: > On Sun, 21 Feb 2016, Robert Jarzmik wrote: > Please, have a look at > http://git.linuxtv.org/gliakhovetski/v4l-dvb.git/log/?h=for-4.6-2 > If all is good there, no need for a v6 Thanks for fixing the *_dma_irq() mess, and sorry for that. And I just tested your

[PATCH] firmware: fw_cfg register offsets on supported architectures only

Refrain from defining default fw_cfg register offsets on unsupported architectures -- throw an error instead. If QEMU were to add fw_cfg support on additional architectures, we should add them to the FW_CFG_SYSFS depends statement in drivers/firmware/Kconfig, and provide default values for

[PATCH] firmware: fw_cfg register offsets on supported architectures only

Refrain from defining default fw_cfg register offsets on unsupported architectures -- throw an error instead. If QEMU were to add fw_cfg support on additional architectures, we should add them to the FW_CFG_SYSFS depends statement in drivers/firmware/Kconfig, and provide default values for

Re: [PATCH v3 3/5] dell-wmi: enable receiving WMI events on Dell Vostro V131

On Mon, Feb 22, 2016 at 09:56:50AM +0100, Michał Kępień wrote: > > > /* > > > * Certain keys are flagged as KE_IGNORE. All of these are either > > > * notifications (rather than requests for change) or are also sent > > > @@ -513,6 +533,7 @@ static int __init dell_wmi_init(void) > > > { > >

Re: [PATCH v3 3/5] dell-wmi: enable receiving WMI events on Dell Vostro V131

On Mon, Feb 22, 2016 at 09:56:50AM +0100, Michał Kępień wrote: > > > /* > > > * Certain keys are flagged as KE_IGNORE. All of these are either > > > * notifications (rather than requests for change) or are also sent > > > @@ -513,6 +533,7 @@ static int __init dell_wmi_init(void) > > > { > >

[PATCH 8/8] drm: msm: separate out module driver registration

The msm driver currently has a single module_init() function but consists of multiple modules that each register a platform driver. This changes the msm_drm_register() function to not call the other functions but instead rely on module load order and/or link order to ensure that the other modules

[PATCH 8/8] drm: msm: separate out module driver registration

The msm driver currently has a single module_init() function but consists of multiple modules that each register a platform driver. This changes the msm_drm_register() function to not call the other functions but instead rely on module load order and/or link order to ensure that the other modules

[PATCH 6/8] drm: msm: move EDP into separate module

Moving around the Makefile for EDP caused a link error with the main driver referring to a builtin module that has no exported symbols: drivers/gpu/built-in.o: In function `msm_drm_register': :(.init.text+0x654): undefined reference to `msm_edp_register' This changes the EDP symbol to a

[PATCH 6/8] drm: msm: move EDP into separate module

Moving around the Makefile for EDP caused a link error with the main driver referring to a builtin module that has no exported symbols: drivers/gpu/built-in.o: In function `msm_drm_register': :(.init.text+0x654): undefined reference to `msm_edp_register' This changes the EDP symbol to a

[PATCH 5/8] drm: msm: move DSI into separate module

Moving around the Makefile for DSI caused a link error with the main driver referring to a builtin module that has no exported symbols: drivers/gpu/built-in.o: In function `msm_drm_register': :(.init.text+0x654): undefined reference to `msm_dsi_register' This changes the DSI symbol to a

[PATCH 5/8] drm: msm: move DSI into separate module

Moving around the Makefile for DSI caused a link error with the main driver referring to a builtin module that has no exported symbols: drivers/gpu/built-in.o: In function `msm_drm_register': :(.init.text+0x654): undefined reference to `msm_dsi_register' This changes the DSI symbol to a

[PATCH 4/8] drm: msm: split out GEM code into helper module

The GEM code is used by dsi, so it can't be part of the main module. This exports all functions that are called by other code, and puts it into the helper module. Signed-off-by: Arnd Bergmann --- drivers/gpu/drm/msm/Makefile | 3 +-- drivers/gpu/drm/msm/msm_gem.c | 29

[PATCH 4/8] drm: msm: split out GEM code into helper module

The GEM code is used by dsi, so it can't be part of the main module. This exports all functions that are called by other code, and puts it into the helper module. Signed-off-by: Arnd Bergmann --- drivers/gpu/drm/msm/Makefile | 3 +-- drivers/gpu/drm/msm/msm_gem.c | 29

[PATCH 3/8] drm: msm: split out fence and iotrace modules

This is a preparation for having edp, dsi and hdmi in separate modules. Those three drivers depend on the iotrace code and, and edp depends on gem, which in turn depends on the fence. With this change, those two pieces of the main driver can be loaded first, to resolve circular dependencies.

[PATCH 3/8] drm: msm: split out fence and iotrace modules

This is a preparation for having edp, dsi and hdmi in separate modules. Those three drivers depend on the iotrace code and, and edp depends on gem, which in turn depends on the fence. With this change, those two pieces of the main driver can be loaded first, to resolve circular dependencies.

[PATCH 2/8] drm: msm: rename module

msm.ko is not an appropriate name for a module that drives a specific device on the msm platform. This changes the name to drm_msm.ko to have something that won't conflict with any other module name. Signed-off-by: Arnd Bergmann --- drivers/gpu/drm/msm/Makefile | 12 ++--

[PATCH 2/8] drm: msm: rename module

msm.ko is not an appropriate name for a module that drives a specific device on the msm platform. This changes the name to drm_msm.ko to have something that won't conflict with any other module name. Signed-off-by: Arnd Bergmann --- drivers/gpu/drm/msm/Makefile | 12 ++-- 1 file

Re: [PATCH v2 3/3] vfs: Use per-cpu list for superblock's inode list

On Mon, Feb 22, 2016 at 02:04:35PM +0100, Jan Kara wrote: > On Mon 22-02-16 13:12:22, Peter Zijlstra wrote: > > On Mon, Feb 22, 2016 at 12:54:35PM +0100, Jan Kara wrote: > > > > Also, I think fsnotify_unmount_inodes() (as per mainline) is missing a > > > > final iput(need_iput) at the very end,

Re: [PATCH v2 3/3] vfs: Use per-cpu list for superblock's inode list

On Mon, Feb 22, 2016 at 02:04:35PM +0100, Jan Kara wrote: > On Mon 22-02-16 13:12:22, Peter Zijlstra wrote: > > On Mon, Feb 22, 2016 at 12:54:35PM +0100, Jan Kara wrote: > > > > Also, I think fsnotify_unmount_inodes() (as per mainline) is missing a > > > > final iput(need_iput) at the very end,

[PATCH 1/8] drm: msm: rename hdmi symbols

Global symbols in the kernel should be prefixed by the name of the subsystem and/or driver to avoid conflicts when all code is built-in. In this case, function names like 'hdmi_register' or 'hdmi_set_mode' are way too generic for an MSM specific DRM driver, so I'm renaming them all to msm_hdmi_*

[PATCH 1/8] drm: msm: rename hdmi symbols

Global symbols in the kernel should be prefixed by the name of the subsystem and/or driver to avoid conflicts when all code is built-in. In this case, function names like 'hdmi_register' or 'hdmi_set_mode' are way too generic for an MSM specific DRM driver, so I'm renaming them all to msm_hdmi_*

Re: "Age" of git.kernel.org isn't right?

Toralf Förster: > Looking here > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v4.4.2 > I see 12 hours here for 1cb8570b (4.4.2 tag) which is about 6 hours away from > the right value, or ? > Hhm, pressing F5 changes the column "Age" to the expected

Re: "Age" of git.kernel.org isn't right?

Toralf Förster: > Looking here > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v4.4.2 > I see 12 hours here for 1cb8570b (4.4.2 tag) which is about 6 hours away from > the right value, or ? > Hhm, pressing F5 changes the column "Age" to the expected

[PATCH v2 2/3] ACPI/NFIT: Add NVDIMM ID "id" under sysfs

ACPI 6.1, section 5.2.25.9, defines an identifier for an NVDIMM. Change the NFIT driver to create read-only "id" file under NVDIMM's nfit directory of sysfs, which shows the NVDIMM ID. Signed-off-by: Toshi Kani Cc: Rafael J. Wysocki Cc: Dan Williams

[PATCH v2 0/3] ACPI 6.1 update for NFIT Control Region Structure

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs defined as SPD values are arrays of bytes. The spec clarified that they need to

[PATCH v2 2/3] ACPI/NFIT: Add NVDIMM ID "id" under sysfs

ACPI 6.1, section 5.2.25.9, defines an identifier for an NVDIMM. Change the NFIT driver to create read-only "id" file under NVDIMM's nfit directory of sysfs, which shows the NVDIMM ID. Signed-off-by: Toshi Kani Cc: Rafael J. Wysocki Cc: Dan Williams Cc: Robert Elliott ---

[PATCH v2 0/3] ACPI 6.1 update for NFIT Control Region Structure

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs defined as SPD values are arrays of bytes. The spec clarified that they need to

[PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to comply ACPI 6.1

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs defined as SPD values are arrays of bytes. The spec clarified that they need to

[PATCH v2 3/3] nfit_test: Update SPD ID init handlings

Update the test code that initializes SPD IDs of NFIT control region structures. nfit_set_spd_id() is added to handle initialization of the SPD IDs, which are arrays of bytes. Signed-off-by: Toshi Kani Cc: Dan Williams Cc: Rafael J. Wysocki

[PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to comply ACPI 6.1

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs defined as SPD values are arrays of bytes. The spec clarified that they need to

[PATCH v2 3/3] nfit_test: Update SPD ID init handlings

Update the test code that initializes SPD IDs of NFIT control region structures. nfit_set_spd_id() is added to handle initialization of the SPD IDs, which are arrays of bytes. Signed-off-by: Toshi Kani Cc: Dan Williams Cc: Rafael J. Wysocki --- tools/testing/nvdimm/test/nfit.c | 64

[PATCH] clk: h8300: Properly cast to __iomem pointer

Sparse complains here because we dropped the __iomem annotation when casting the aligned address. Add __iomem back so that sparse stops complaining. Cc: Yoshinori Sato Cc: Signed-off-by: Stephen Boyd ---

[PATCH] clk: h8300: Properly cast to __iomem pointer

Sparse complains here because we dropped the __iomem annotation when casting the aligned address. Add __iomem back so that sparse stops complaining. Cc: Yoshinori Sato Cc: Signed-off-by: Stephen Boyd --- drivers/clk/h8300/clk-div.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] clk: qcom: msm8960: fix ce3_core clk enable register

On 02/22, Srinivas Kandagatla wrote: > This patch corrects the enable register offset which is actually 0x36cc > instead of 0x36c4 > > Signed-off-by: Srinivas Kandagatla > --- Applied to clk-next + added fixes tag -- Qualcomm Innovation Center, Inc. is a member

Re: [PATCH] clk: qcom: msm8960: fix ce3_core clk enable register

On 02/22, Srinivas Kandagatla wrote: > This patch corrects the enable register offset which is actually 0x36cc > instead of 0x36c4 > > Signed-off-by: Srinivas Kandagatla > --- Applied to clk-next + added fixes tag -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux

[PATCH 3/9] clk: gpio: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the type here. Signed-off-by: Stephen Boyd --- drivers/clk/clk-gpio.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH 5/9] clk: st: Remove impossible check for of_clk_get_parent_count() < 0

The checks for < 0 are impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Gabriel Fernandez Signed-off-by: Stephen Boyd --- drivers/clk/st/clk-flexgen.c | 4 ++--

[PATCH 3/9] clk: gpio: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the type here. Signed-off-by: Stephen Boyd --- drivers/clk/clk-gpio.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/clk/clk-gpio.c

[PATCH 5/9] clk: st: Remove impossible check for of_clk_get_parent_count() < 0

The checks for < 0 are impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Gabriel Fernandez Signed-off-by: Stephen Boyd --- drivers/clk/st/clk-flexgen.c | 4 ++-- drivers/clk/st/clkgen-mux.c | 4 ++-- 2 files changed, 4

Re: 4.5-rc4 kernel is failed to bootup on CN6880

On 02/22/2016 11:15 AM, Yang Shi wrote: On 2/22/2016 4:43 AM, Aaro Koskinen wrote: Hi, On Fri, Feb 19, 2016 at 05:12:41PM -0800, Yang Shi wrote: I tried to boot 4.5-rc4 kernel on my CN6880 board, but it is failed at booting up secondary cores. The error is: With v4.5-rc5, EBB6800 is booting

[PATCH 1/9] clk: Make of_clk_get_parent_count() return unsigned ints

Russell King recently pointed out a bug in the clk-gpio code where it fails to register the clk if of_clk_get_parent_count() returns an error because the "clocks" property isn't present in the DT node. If we're trying to count parents from DT we'd like to know the count, not if there is a "clocks"

Re: 4.5-rc4 kernel is failed to bootup on CN6880

On 02/22/2016 11:15 AM, Yang Shi wrote: On 2/22/2016 4:43 AM, Aaro Koskinen wrote: Hi, On Fri, Feb 19, 2016 at 05:12:41PM -0800, Yang Shi wrote: I tried to boot 4.5-rc4 kernel on my CN6880 board, but it is failed at booting up secondary cores. The error is: With v4.5-rc5, EBB6800 is booting

[PATCH 1/9] clk: Make of_clk_get_parent_count() return unsigned ints

Russell King recently pointed out a bug in the clk-gpio code where it fails to register the clk if of_clk_get_parent_count() returns an error because the "clocks" property isn't present in the DT node. If we're trying to count parents from DT we'd like to know the count, not if there is a "clocks"

[PATCH 7/9] clk: ti: Update for of_clk_get_parent_count() returning unsigned int

Change the types here to unsigned int instead of int and update the checks for == 0 instead < 1 to be more explicit about what's going on now that of_clk_get_parent_count() has changed return types. Cc: Tero Kristo Signed-off-by: Stephen Boyd ---

[PATCH 7/9] clk: ti: Update for of_clk_get_parent_count() returning unsigned int

Change the types here to unsigned int instead of int and update the checks for == 0 instead < 1 to be more explicit about what's going on now that of_clk_get_parent_count() has changed return types. Cc: Tero Kristo Signed-off-by: Stephen Boyd --- drivers/clk/ti/clockdomain.c | 2 +-

[PATCH 8/9] usb: dwc3: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Felipe Balbi Cc: Signed-off-by: Stephen Boyd --- Please ack so this can go through clk tree

[PATCH 8/9] usb: dwc3: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Felipe Balbi Cc: Signed-off-by: Stephen Boyd --- Please ack so this can go through clk tree along with patch 1. drivers/usb/dwc3/dwc3-of-simple.c | 9

[PATCH 6/9] clk: sunxi: Use proper type for of_clk_get_parent_count() return value

The return type of of_clk_get_parent_count() is an unsigned int now, so let's update the code here to be more explicit about the range of values we can test for. Cc: Maxime Ripard Cc: Chen-Yu Tsai Signed-off-by: Stephen Boyd

[PATCH 4/9] clk: h8300: Remove impossible check for of_clk_get_parent_count()

The checks for < 1 can be simplified now that of_clk_get_parent_count() returns an unsigned int. Update the code to reflect the int to unsigned int change. Cc: Yoshinori Sato Cc: Signed-off-by: Stephen Boyd

[PATCH 9/9] simplefb: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Hans de Goede Cc: Jean-Christophe Plagniol-Villard Cc: Tomi Valkeinen Cc:

[PATCH 6/9] clk: sunxi: Use proper type for of_clk_get_parent_count() return value

The return type of of_clk_get_parent_count() is an unsigned int now, so let's update the code here to be more explicit about the range of values we can test for. Cc: Maxime Ripard Cc: Chen-Yu Tsai Signed-off-by: Stephen Boyd --- drivers/clk/sunxi/clk-sun6i-ar100.c | 2 +- 1 file changed, 1

[PATCH 4/9] clk: h8300: Remove impossible check for of_clk_get_parent_count()

The checks for < 1 can be simplified now that of_clk_get_parent_count() returns an unsigned int. Update the code to reflect the int to unsigned int change. Cc: Yoshinori Sato Cc: Signed-off-by: Stephen Boyd --- drivers/clk/h8300/clk-div.c | 4 ++-- drivers/clk/h8300/clk-h8s2678.c | 4 ++--

[PATCH 9/9] simplefb: Remove impossible check for of_clk_get_parent_count() < 0

The check for < 0 is impossible now that of_clk_get_parent_count() returns an unsigned int. Simplify the code and update the types. Cc: Hans de Goede Cc: Jean-Christophe Plagniol-Villard Cc: Tomi Valkeinen Cc: Signed-off-by: Stephen Boyd --- Please ack so this can go through clk tree along

[PATCH 0/9] Change return type of of_clk_get_parent_count() to unsigned

Russell King recently pointed out that of_clk_get_parent_count() can return a negative number if the "clocks" property isn't present in a node. Upon investigating all the callers of this API, none of the them seem to care about that case, and furthermore some callers are assigning the return value

[PATCH 0/9] Change return type of of_clk_get_parent_count() to unsigned

Russell King recently pointed out that of_clk_get_parent_count() can return a negative number if the "clocks" property isn't present in a node. Upon investigating all the callers of this API, none of the them seem to care about that case, and furthermore some callers are assigning the return value

[PATCH 2/9] clk: at91: Remove impossible checks for of_clk_get_parent_count()

These checks for < 0 are impossible now that of_clk_get_parent_count() returns an unsigned int. Change the checks for == 0 and update the type. Cc: Boris Brezillon Signed-off-by: Stephen Boyd --- drivers/clk/at91/clk-generated.c| 4

[PATCH 2/9] clk: at91: Remove impossible checks for of_clk_get_parent_count()

These checks for < 0 are impossible now that of_clk_get_parent_count() returns an unsigned int. Change the checks for == 0 and update the type. Cc: Boris Brezillon Signed-off-by: Stephen Boyd --- drivers/clk/at91/clk-generated.c| 4 ++-- drivers/clk/at91/clk-main.c | 4 ++--

Re: [PATCH v1] ARM: dts: nitrogen6x: add USB host 1 support

On Mon, Feb 22, 2016 at 5:48 PM, Troy Kisky wrote: > I'm ok with this patch, but a more correct fix would be to add a > reset-gpios to usbh1 instead, as this is a reset pin for > a usb hub. So if nobody else has a problem, The problem is that such solution does

Re: [PATCH v1] ARM: dts: nitrogen6x: add USB host 1 support

On Mon, Feb 22, 2016 at 5:48 PM, Troy Kisky wrote: > I'm ok with this patch, but a more correct fix would be to add a > reset-gpios to usbh1 instead, as this is a reset pin for > a usb hub. So if nobody else has a problem, The problem is that such solution does not exist today. Peter Chen has

Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region()

On 02/22/2016 05:49 AM, Alan Cox wrote: >> we have some good alternatives in the form of bus and platform >> drivers that >> can manage the appropriate serialization and keep things from >> stomping >> on one another. > > It's not used much, especially nowdays. The use case is basically multi >

Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region()

On 02/22/2016 05:49 AM, Alan Cox wrote: >> we have some good alternatives in the form of bus and platform >> drivers that >> can manage the appropriate serialization and keep things from >> stomping >> on one another. > > It's not used much, especially nowdays. The use case is basically multi >

Re: [PATCH] netcp: fix typo in netcp_setup_tc

From: Arnd Bergmann Date: Mon, 22 Feb 2016 21:50:39 +0100 > A change to the prototype of netcp_setup_tc() missed a '*' > character, which broke compilation of hte netcp driver: > > drivers/net/ethernet/ti/netcp_core.c: In function 'netcp_setup_tc': >

Re: [PATCH] netcp: fix typo in netcp_setup_tc

From: Arnd Bergmann Date: Mon, 22 Feb 2016 21:50:39 +0100 > A change to the prototype of netcp_setup_tc() missed a '*' > character, which broke compilation of hte netcp driver: > > drivers/net/ethernet/ti/netcp_core.c: In function 'netcp_setup_tc': >

[PATCH] netcp: fix typo in netcp_setup_tc

A change to the prototype of netcp_setup_tc() missed a '*' character, which broke compilation of hte netcp driver: drivers/net/ethernet/ti/netcp_core.c: In function 'netcp_setup_tc': drivers/net/ethernet/ti/netcp_core.c:1839:31: error: invalid type argument of '->' (have 'struct tc_to_netdev')

[PATCH] netcp: fix typo in netcp_setup_tc

A change to the prototype of netcp_setup_tc() missed a '*' character, which broke compilation of hte netcp driver: drivers/net/ethernet/ti/netcp_core.c: In function 'netcp_setup_tc': drivers/net/ethernet/ti/netcp_core.c:1839:31: error: invalid type argument of '->' (have 'struct tc_to_netdev')

Re: [PATCH 08/10] x86/xsaves: Fix PTRACE frames for XSAVES

On Mon, Feb 22, 2016 at 12:00:02PM -0800, Dave Hansen wrote: > On 02/22/2016 11:00 AM, Yu-cheng Yu wrote: > > + if (xsave->header.xfeatures & XFEATURE_MASK_SUPERVISOR) > > + xsave->header.xfeatures = xfeatures | XFEATURE_MASK_SUPERVISOR; > > + else > > +

Re: [PATCH 08/10] x86/xsaves: Fix PTRACE frames for XSAVES

On Mon, Feb 22, 2016 at 12:00:02PM -0800, Dave Hansen wrote: > On 02/22/2016 11:00 AM, Yu-cheng Yu wrote: > > + if (xsave->header.xfeatures & XFEATURE_MASK_SUPERVISOR) > > + xsave->header.xfeatures = xfeatures | XFEATURE_MASK_SUPERVISOR; > > + else > > +

Re: [PATCH v1] ARM: dts: nitrogen6x: add USB host 1 support

On 2/22/2016 1:03 PM, Peter Seiderer wrote: > Regulator stuff and pin configuration copied from imx6qdl-nitrogen6_max.dtsi > and checked against Boundary Devices linux kernel tree ([1]). > > [1] >

Re: [PATCH v1] ARM: dts: nitrogen6x: add USB host 1 support

On 2/22/2016 1:03 PM, Peter Seiderer wrote: > Regulator stuff and pin configuration copied from imx6qdl-nitrogen6_max.dtsi > and checked against Boundary Devices linux kernel tree ([1]). > > [1] >

Re: [PATCH] lkdtm: add test for executing .rodata

On Thu, Feb 18, 2016 at 1:27 PM, PaX Team wrote: > On 18 Feb 2016 at 12:34, Ard Biesheuvel wrote: > >> However, that does not fix the issue Kees is trying to solve, where a >> .rodata section is emitted with the "x" bit set, which causes the >> linker to complain: >> >>

Re: [PATCH] lkdtm: add test for executing .rodata

On Thu, Feb 18, 2016 at 1:27 PM, PaX Team wrote: > On 18 Feb 2016 at 12:34, Ard Biesheuvel wrote: > >> However, that does not fix the issue Kees is trying to solve, where a >> .rodata section is emitted with the "x" bit set, which causes the >> linker to complain: >> >> /tmp/cc50ffWw.s: Assembler

Re: [PATCH 07/10] x86/xsaves: Fix init_fpstate.header.xcomp_bv

On Mon, Feb 22, 2016 at 11:55:50AM -0800, Dave Hansen wrote: > On 02/22/2016 10:59 AM, Yu-cheng Yu wrote: > > This actually does not apply to XSAVES as XSAVES uses optimization. After > > init, all components are in INIT and not MODIFIED state and will not be > > saved. There is no need of setting

Re: [PATCH 07/10] x86/xsaves: Fix init_fpstate.header.xcomp_bv

On Mon, Feb 22, 2016 at 11:55:50AM -0800, Dave Hansen wrote: > On 02/22/2016 10:59 AM, Yu-cheng Yu wrote: > > This actually does not apply to XSAVES as XSAVES uses optimization. After > > init, all components are in INIT and not MODIFIED state and will not be > > saved. There is no need of setting

Re: [patch 3/6] Staging: gdm72xx: make "len" unsigned

Hi Dan, [auto build test WARNING on staging/staging-testing] [also build test WARNING on v4.5-rc5 next-20160222] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Dan-Carpenter/staging-gdm72xx

Re: [patch 3/6] Staging: gdm72xx: make "len" unsigned

Hi Dan, [auto build test WARNING on staging/staging-testing] [also build test WARNING on v4.5-rc5 next-20160222] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Dan-Carpenter/staging-gdm72xx

Re: [patch V2 18/28] x86/perf/intel_rapl: Make Knights Landings support functional

On Mon, Feb 22, 2016 at 11:06:56AM -, Thomas Gleixner wrote: > The Knights Landings support added the events and the detection case, but then > returns 0 without actually initializing the driver. > > Fixes: 3a2a7797326a4 "perf/x86/intel/rapl: Add support for Knights Landing > (KNL)" >

Re: [patch V2 18/28] x86/perf/intel_rapl: Make Knights Landings support functional

On Mon, Feb 22, 2016 at 11:06:56AM -, Thomas Gleixner wrote: > The Knights Landings support added the events and the detection case, but then > returns 0 without actually initializing the driver. > > Fixes: 3a2a7797326a4 "perf/x86/intel/rapl: Add support for Knights Landing > (KNL)" >

<    5   6   7   8   9   10   11   12   13   14   >