Re: linux-next: Signed-off-by missing for commit in the bluetooth tree

Hi, On Sat, Dec 30, 2017, Stephen Rothwell wrote: > On Sat, 30 Dec 2017 10:25:52 +1100 Stephen Rothwell > wrote: > > Commit > > > > 0a03f98b98c2 ("Bluetooth: Add a new 04ca:3015 QCA_ROME device") > > > > is missing a Signed-off-by from its . >

Re: linux-next: Signed-off-by missing for commit in the bluetooth tree

Hi, On Sat, Dec 30, 2017, Stephen Rothwell wrote: > On Sat, 30 Dec 2017 10:25:52 +1100 Stephen Rothwell > wrote: > > Commit > > > > 0a03f98b98c2 ("Bluetooth: Add a new 04ca:3015 QCA_ROME device") > > > > is missing a Signed-off-by from its . > ^ >

Re: general protection fault in skb_segment

> syzkaller hit the following crash on > 37759fa6d0fa9e4d6036d19ac12f555bfc0aeafd > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > C reproducer is attached > syzkaller reproducer is attached. See

Re: general protection fault in skb_segment

> syzkaller hit the following crash on > 37759fa6d0fa9e4d6036d19ac12f555bfc0aeafd > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > C reproducer is attached > syzkaller reproducer is attached. See

[PATCH] f2fs: check segment type before recover data

In some case, the node blocks has wrong blkaddr whose segment type is NODE, e.g., recover inode has missing xattr flag and the blkaddr is in the xattr range. Since fsck.f2fs does not check the recovery nodes, this will cause __f2fs_replace_block change the curseg of node and do the

[PATCH] f2fs: check segment type before recover data

In some case, the node blocks has wrong blkaddr whose segment type is NODE, e.g., recover inode has missing xattr flag and the blkaddr is in the xattr range. Since fsck.f2fs does not check the recovery nodes, this will cause __f2fs_replace_block change the curseg of node and do the

Re: [PATCH] futex: use fault_in to avoid infinite loop

Peter, On Wed, Dec 6, 2017 at 10:40 PM, Peter Zijlstra wrote: > On Wed, Dec 06, 2017 at 05:04:00PM +0100, Peter Zijlstra wrote: >> On Wed, Dec 06, 2017 at 10:21:07PM +0800, Cheng Jian wrote: >> > It will cause softlockup(infinite loop) in kernel >> > space when we use

Re: [PATCH] futex: use fault_in to avoid infinite loop

Peter, On Wed, Dec 6, 2017 at 10:40 PM, Peter Zijlstra wrote: > On Wed, Dec 06, 2017 at 05:04:00PM +0100, Peter Zijlstra wrote: >> On Wed, Dec 06, 2017 at 10:21:07PM +0800, Cheng Jian wrote: >> > It will cause softlockup(infinite loop) in kernel >> > space when we use SYS_set_robust_list in

Re: [PATCH 2/2] Introduce __cond_lock_err

On Wed, Dec 27, 2017 at 03:28:54PM +0100, Luc Van Oostenryck wrote: > On Fri, Dec 22, 2017 at 04:31:12AM -0800, Matthew Wilcox wrote: > > On Thu, Dec 21, 2017 at 08:21:20PM -0800, Josh Triplett wrote: > > > > While I've got you, I've been looking at some other sparse warnings from > > this file.

Re: [PATCH 2/2] Introduce __cond_lock_err

On Wed, Dec 27, 2017 at 03:28:54PM +0100, Luc Van Oostenryck wrote: > On Fri, Dec 22, 2017 at 04:31:12AM -0800, Matthew Wilcox wrote: > > On Thu, Dec 21, 2017 at 08:21:20PM -0800, Josh Triplett wrote: > > > > While I've got you, I've been looking at some other sparse warnings from > > this file.

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

On Wed, Dec 27, 2017 at 10:10:34AM +0100, Brice Goglin wrote: > > Perhaps we can enlist /proc/iomem or a similar enumeration interface > > to tell userspace the NUMA node and whether the kernel thinks it has > > better or worse performance characteristics relative to base > > system-RAM, i.e. new

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

On Wed, Dec 27, 2017 at 10:10:34AM +0100, Brice Goglin wrote: > > Perhaps we can enlist /proc/iomem or a similar enumeration interface > > to tell userspace the NUMA node and whether the kernel thinks it has > > better or worse performance characteristics relative to base > > system-RAM, i.e. new

[no subject]

Hello ; I have a proposal for you,kindly get back to me soon. Mrs Christy Walton.

[no subject]

Hello ; I have a proposal for you,kindly get back to me soon. Mrs Christy Walton.

Re: [PATCH 11/20] nvmem: meson-efuse: Convert to use devm_nvmem_register()

Hi Andrey, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc5] [cannot apply to next-20171222] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 11/20] nvmem: meson-efuse: Convert to use devm_nvmem_register()

Hi Andrey, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc5] [cannot apply to next-20171222] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: About the try to remove cross-release feature entirely by Ingo

On Fri, Dec 29, 2017 at 04:28:51PM +0900, Byungchul Park wrote: > On Thu, Dec 28, 2017 at 10:51:46PM -0500, Theodore Ts'o wrote: > > On Fri, Dec 29, 2017 at 10:47:36AM +0900, Byungchul Park wrote: > > > > > >(1) The best way: To classify all waiters correctly. > > > > It's really not all

Re: About the try to remove cross-release feature entirely by Ingo

On Fri, Dec 29, 2017 at 04:28:51PM +0900, Byungchul Park wrote: > On Thu, Dec 28, 2017 at 10:51:46PM -0500, Theodore Ts'o wrote: > > On Fri, Dec 29, 2017 at 10:47:36AM +0900, Byungchul Park wrote: > > > > > >(1) The best way: To classify all waiters correctly. > > > > It's really not all

RE: [PATCH v3] igb: Free IRQs when device is hotplugged

> From: netdev-ow...@vger.kernel.org [mailto:netdev- > ow...@vger.kernel.org] On Behalf Of Lyude Paul > Sent: Tuesday, December 12, 2017 11:32 AM > To: intel-wired-...@lists.osuosl.org > Cc: Fujinaka, Todd ; Stephen Hemminger > ;

RE: [PATCH v3] igb: Free IRQs when device is hotplugged

> From: netdev-ow...@vger.kernel.org [mailto:netdev- > ow...@vger.kernel.org] On Behalf Of Lyude Paul > Sent: Tuesday, December 12, 2017 11:32 AM > To: intel-wired-...@lists.osuosl.org > Cc: Fujinaka, Todd ; Stephen Hemminger > ; sta...@vger.kernel.org; Kirsher, Jeffrey T > ;

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: > > As far as I know, none of the licenses explicitly say > > copyright license must be on each file. Just that the distribution of > > source must include the copyright and license statement. Exactly how > > that is done is

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: > > As far as I know, none of the licenses explicitly say > > copyright license must be on each file. Just that the distribution of > > source must include the copyright and license statement. Exactly how > > that is done is

Re: [PATCH v2 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC

On 2017-12-29 23:43, Keith Busch wrote: On Fri, Dec 29, 2017 at 11:30:02PM +0530, p...@codeaurora.org wrote: On 2017-12-29 22:53, Keith Busch wrote: > 2. A DPC event suppresses the error message required for the Linux > AER driver to run. How can AER and DPC run concurrently? I afraid I could

Re: [PATCH v2 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC

On 2017-12-29 23:43, Keith Busch wrote: On Fri, Dec 29, 2017 at 11:30:02PM +0530, p...@codeaurora.org wrote: On 2017-12-29 22:53, Keith Busch wrote: > 2. A DPC event suppresses the error message required for the Linux > AER driver to run. How can AER and DPC run concurrently? I afraid I could

[PATCH net-next 2/2] net: stmmac: Allow debug prints of frame_len/COE

There is no reason not to allow printing the frame_len/COE value and put that under a check for ETH_FRAME_LEN, drop it so we can see what the descriptor reports. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 5 ++--- 1 file

[PATCH net-next 2/2] net: stmmac: Allow debug prints of frame_len/COE

There is no reason not to allow printing the frame_len/COE value and put that under a check for ETH_FRAME_LEN, drop it so we can see what the descriptor reports. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 5 ++--- 1 file changed, 2 insertions(+), 3

[PATCH net-next 1/2] net: stmmac: Pad ring number with zeroes in display_ring()

Make the printing of the ring number consistent and properly aligned by padding the ring number with up to 3 zeroes, which covers the maximum ring size. This makes it a lot easier to see outliers in debug prints. Signed-off-by: Florian Fainelli ---

[PATCH net-next 0/2] net: stmmac: Couple of debug prints improvements

Hi all, While working on a particular problem, I had to turn on debug prints and found them to be useful, but could deserve some improvements in order to help debug situations. Florian Fainelli (2): net: stmmac: Pad ring number with zeroes in display_ring() net: stmmac: Allow debug prints of

[PATCH net-next 1/2] net: stmmac: Pad ring number with zeroes in display_ring()

Make the printing of the ring number consistent and properly aligned by padding the ring number with up to 3 zeroes, which covers the maximum ring size. This makes it a lot easier to see outliers in debug prints. Signed-off-by: Florian Fainelli ---

[PATCH net-next 0/2] net: stmmac: Couple of debug prints improvements

Hi all, While working on a particular problem, I had to turn on debug prints and found them to be useful, but could deserve some improvements in order to help debug situations. Florian Fainelli (2): net: stmmac: Pad ring number with zeroes in display_ring() net: stmmac: Allow debug prints of

[PATCH 4/5] sched/isolation: Residual 1Hz scheduler tick offload

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand no interruption at all, or want to minimize them. Adding the boot parameter "isolcpus=nohz_offload" will now outsource

[PATCH 1/5] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney

[PATCH 5/5] sched/isolation: Document "nohz_offload" flag

Document the interface to offload the 1Hz scheduler tick in full dynticks mode. Also improve the comment about the existing "nohz" flag in order to differentiate its behaviour. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter

[PATCH 0/5] isolation: 1Hz residual tick offloading v3

No big change in this row, just a build failure fix on patch 4/5 due to sched_tick_start()/sched_tick_stop() not having off cases. If no more comment arise, I'll do a pull request in a few days. git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git timers/0z-v3 HEAD:

[PATCH 4/5] sched/isolation: Residual 1Hz scheduler tick offload

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand no interruption at all, or want to minimize them. Adding the boot parameter "isolcpus=nohz_offload" will now outsource

[PATCH 1/5] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc: Wanpeng Li Cc: Ingo Molnar ---

[PATCH 5/5] sched/isolation: Document "nohz_offload" flag

Document the interface to offload the 1Hz scheduler tick in full dynticks mode. Also improve the comment about the existing "nohz" flag in order to differentiate its behaviour. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith

[PATCH 0/5] isolation: 1Hz residual tick offloading v3

No big change in this row, just a build failure fix on patch 4/5 due to sched_tick_start()/sched_tick_stop() not having off cases. If no more comment arise, I'll do a pull request in a few days. git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git timers/0z-v3 HEAD:

[PATCH 3/5] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc:

[PATCH 3/5] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas

[PATCH 2/5] sched/isolation: Add scheduler tick offloading interface

Add the boot option that will allow us to offload the 1Hz scheduler tick to the housekeeping CPU. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike

[PATCH 2/5] sched/isolation: Add scheduler tick offloading interface

Add the boot option that will allow us to offload the 1Hz scheduler tick to the housekeeping CPU. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner

Re: [PATCH] Staging: ncpfs: dir: fixed a bracket coding style issue

On Fri, 29 Dec 2017 15:27:13 -0800 Santha Meena Ramamoorthy wrote: > Fixed a coding style issue. > > Signed-off-by: Santha Meena Ramamoorthy Read the TODO please

Re: [PATCH] Staging: ncpfs: dir: fixed a bracket coding style issue

On Fri, 29 Dec 2017 15:27:13 -0800 Santha Meena Ramamoorthy wrote: > Fixed a coding style issue. > > Signed-off-by: Santha Meena Ramamoorthy Read the TODO please

Re: 4.14.9 doesn't boot (regression)

On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > (Also, Josh, the oops code should have printed the contents of the > struct pt_regs at the top of the DF stack. Any idea why it didn't?) Looking at one of the dumps: [ 392.774879] NMI backtrace for cpu 0 [ 392.774881] CPU:

Re: 4.14.9 doesn't boot (regression)

On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > (Also, Josh, the oops code should have printed the contents of the > struct pt_regs at the top of the DF stack. Any idea why it didn't?) Looking at one of the dumps: [ 392.774879] NMI backtrace for cpu 0 [ 392.774881] CPU:

Re: [PATCH v2 1/2] Input: edt-ft5x06 - Add support for regulator

Hi Mylène, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.15-rc5 next-20171222] [cannot apply to input/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 1/2] Input: edt-ft5x06 - Add support for regulator

Hi Mylène, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.15-rc5 next-20171222] [cannot apply to input/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] Input: fix semicolon.cocci warnings

From: Fengguang Wu drivers/input/touchscreen/edt-ft5x06.c:1004:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: 5969d946e8aa ("Input: edt-ft5x06 - Add support for regulator") CC: Mylène Josserand

[PATCH] Input: fix semicolon.cocci warnings

From: Fengguang Wu drivers/input/touchscreen/edt-ft5x06.c:1004:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: 5969d946e8aa ("Input: edt-ft5x06 - Add support for regulator") CC: Mylène Josserand Signed-off-by: Fengguang Wu

Re: linux-next: Signed-off-by missing for commit in the tpmdd tree

On Sat, Dec 30, 2017 at 10:32:13AM +1100, Stephen Rothwell wrote: > Hi Jarkko, > > Commit > > c01386d6129f ("tpm: Update MAINTAINERS for Jason Gunthorpe") > > is missing a Signed-off-by from its committer. Thanks Stephen, Jarkko, it started out OK, so you can probably just add it back in?

Re: linux-next: Signed-off-by missing for commit in the tpmdd tree

On Sat, Dec 30, 2017 at 10:32:13AM +1100, Stephen Rothwell wrote: > Hi Jarkko, > > Commit > > c01386d6129f ("tpm: Update MAINTAINERS for Jason Gunthorpe") > > is missing a Signed-off-by from its committer. Thanks Stephen, Jarkko, it started out OK, so you can probably just add it back in?

[RFC PATCH Resend] ksm: allow dedup all tasks memory

ksm by default working only on memory that added by madvice(). And only way get that work on other applications: - Use LD_PRELOAD and libraries - Patch kernel Lets use kernel task list in ksm_scan_thread and add logic to allow ksm import VMA from tasks. That behaviour controlled by new

[RFC PATCH Resend] ksm: allow dedup all tasks memory

ksm by default working only on memory that added by madvice(). And only way get that work on other applications: - Use LD_PRELOAD and libraries - Patch kernel Lets use kernel task list in ksm_scan_thread and add logic to allow ksm import VMA from tasks. That behaviour controlled by new

Re: [GIT pull] x86/pti: The real thing

On Thu, Dec 28, 2017 at 12:34 PM, Thomas Gleixner wrote: > > please pull the latest x86-pti-for-linus git tree from: > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus > > This is the final set of enabling page table isolation on x86: Ok, after

Re: [GIT pull] x86/pti: The real thing

On Thu, Dec 28, 2017 at 12:34 PM, Thomas Gleixner wrote: > > please pull the latest x86-pti-for-linus git tree from: > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus > > This is the final set of enabling page table isolation on x86: Ok, after that late MCORE2

Re: 4.14.9 doesn't boot (regression)

On Fri, Dec 29, 2017 at 5:00 PM, Linus Torvalds wrote: > > Good. I was not feeling so happy about this bug report, but now I can > firmly just blame the gentoo compiler for having some shit-for-brains > "feature". Looks like I can generate similar bad code with the

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 29/12/2017 в 17:04 -0800, Dave Hansen пишет: > On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > > > Does anyone have the results of build that they can > > > share?  (vmlinux, > > > vmlinuz/bzImage, System.map, .config).  That, plus a > >

Re: 4.14.9 doesn't boot (regression)

On Fri, Dec 29, 2017 at 5:00 PM, Linus Torvalds wrote: > > Good. I was not feeling so happy about this bug report, but now I can > firmly just blame the gentoo compiler for having some shit-for-brains > "feature". Looks like I can generate similar bad code with the F26 version of gcc, it's just

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 29/12/2017 в 17:04 -0800, Dave Hansen пишет: > On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > > > Does anyone have the results of build that they can > > > share?  (vmlinux, > > > vmlinuz/bzImage, System.map, .config).  That, plus a > >

[PATCH 01/33] clk_ops: change round_rate() to return unsigned long

Right now it is not possible to return a value larger than LONG_MAX on 32 bit systems. You can pass a rate of ULONG_MAX but can't return anything past LONG_MAX due to the fact both the rounded_rate and negative error codes are represented in the return value of round_rate(). Most implementations

[PATCH 01/33] clk_ops: change round_rate() to return unsigned long

Right now it is not possible to return a value larger than LONG_MAX on 32 bit systems. You can pass a rate of ULONG_MAX but can't return anything past LONG_MAX due to the fact both the rounded_rate and negative error codes are represented in the return value of round_rate(). Most implementations

[PATCH 02/33] clk: core: update divider_round_rate functions to return unsigned long

Returning a long from round_rate() class functions is rooted in the notion that we will propagate a negative number on some class of failure to round a clock rate; however this approach does not scale to 32 bit systems which legitimately round a clock over LONG_MAX as the returned clock rate is

[PATCH 02/33] clk: core: update divider_round_rate functions to return unsigned long

Returning a long from round_rate() class functions is rooted in the notion that we will propagate a negative number on some class of failure to round a clock rate; however this approach does not scale to 32 bit systems which legitimately round a clock over LONG_MAX as the returned clock rate is

[PATCH 08/33] clk: bcm2835: change bcm2835_pll_rate_from_divisors to return unsigned long

bcm2835_pll_rate_from_divisors() returns a value directly as the return value to round_rate(). clk_ops->round_rate() has been changed to an unsigned long so for the sake of completeness and neatness this patch updates the helper function to return the same data-type. Signed-off-by: Bryan

[PATCH 08/33] clk: bcm2835: change bcm2835_pll_rate_from_divisors to return unsigned long

bcm2835_pll_rate_from_divisors() returns a value directly as the return value to round_rate(). clk_ops->round_rate() has been changed to an unsigned long so for the sake of completeness and neatness this patch updates the helper function to return the same data-type. Signed-off-by: Bryan

[PATCH 09/33] clk: bcm2835: change clk_get_rate() helper return type

bcm2835_pll_rate_from_divisor returns a long but the function calling it returns an unsigned long. There's no reason to have a type disparity here so tidy up the return type of bcm2835_pll_rate_from_divisor() from signed to unsigned long. Signed-off-by: Bryan O'Donoghue

[PATCH 09/33] clk: bcm2835: change clk_get_rate() helper return type

bcm2835_pll_rate_from_divisor returns a long but the function calling it returns an unsigned long. There's no reason to have a type disparity here so tidy up the return type of bcm2835_pll_rate_from_divisor() from signed to unsigned long. Signed-off-by: Bryan O'Donoghue Cc: Michael Turquette

[PATCH 07/33] clk: axs10x: change i2s_pll_round_rate return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 07/33] clk: axs10x: change i2s_pll_round_rate return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 06/33] clk: at91: change clk_pll_get_best_div_mul() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 06/33] clk: at91: change clk_pll_get_best_div_mul() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 04/33] clk: omap2: change omap2_round_to_table_rate return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 05/33] clk: at91: update clk_pll_get_best_div_mul to return unsigned long

clk_pll_get_best_div_mul() returns a value directly as the return value to round_rate(). clk_ops->round_rate() has been changed to an unsigned long so for the sake of completeness and neatness this patch updates the helper function to return the same data-type. Signed-off-by: Bryan O'Donoghue

[PATCH 04/33] clk: omap2: change omap2_round_to_table_rate return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 05/33] clk: at91: update clk_pll_get_best_div_mul to return unsigned long

clk_pll_get_best_div_mul() returns a value directly as the return value to round_rate(). clk_ops->round_rate() has been changed to an unsigned long so for the sake of completeness and neatness this patch updates the helper function to return the same data-type. Signed-off-by: Bryan O'Donoghue

[PATCH 10/33] clk: bcm: iproc: change iproc_asiu_clk_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 10/33] clk: bcm: iproc: change iproc_asiu_clk_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 17/33] clk: mvebu: change dove_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 17/33] clk: mvebu: change dove_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 18/33] clk: mxs: change clk_frac_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 18/33] clk: mxs: change clk_frac_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 19/33] clk: nxp: change lpc18xx_pll0_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 20/33] clk: lpc32xx: change clk_hclk_pll_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 19/33] clk: nxp: change lpc18xx_pll0_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 20/33] clk: lpc32xx: change clk_hclk_pll_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 14/33] clk: vc5: change vc5_mux_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 14/33] clk: vc5: change vc5_mux_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 13/33] clk: si514: change si514_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 13/33] clk: si514: change si514_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH] Staging: pi433 - fix ccheckpatch issue, updated include line.

Updated the include of compat.h to fix checkpatch error Signed-off-by: Derek Robson --- drivers/staging/pi433/pi433_if.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c index

[PATCH] Staging: pi433 - fix ccheckpatch issue, updated include line.

Updated the include of compat.h to fix checkpatch error Signed-off-by: Derek Robson --- drivers/staging/pi433/pi433_if.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c index 1d7c50c1ac23..0555c76cea49

[PATCH 21/33] clk: qcom: ipq4019: change clk_cpu_div_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 21/33] clk: qcom: ipq4019: change clk_cpu_div_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 23/33] clk: tegra: change clk_sync_source_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 24/33] clk: tegra: bpmp: change tegra_bpmp_clk_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 23/33] clk: tegra: change clk_sync_source_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 24/33] clk: tegra: bpmp: change tegra_bpmp_clk_round_rate() return logic

This patch updates the round_rate() logic here to return zero instead of a negative number on error. In conjunction with higher-level changes associated with acting on the return value of clk_ops->round_rate() it is then possible to have clk_ops->round_rate() return values from 1 Hz to ULONG_MAX

[PATCH 12/33] clk: cdce925: remove unnecessary long casts on return

Due to the old function signature of clk_ops->round_rate the cdce925 round_rate functions end up doing a cast of an internal unsigned long to a long. After updating clk_ops->round_rate() to be an unsigned long though the cast isn't necessary. Remove the extraneous cast from: -

[PATCH 22/33] clk: sirf: remove unnecessary long cast on return

Due to the old function signature of clk_ops->round_rate pll_clk_round_rate does a cast of an internal unsigned long to a long. After updating clk_ops->round_rate() to be an unsigned long though the cast isn't necessary. Remove the cast now. Signed-off-by: Bryan O'Donoghue

  1   2   3   4   5   6   7   8   9   10   >