Fixed a typo issue in get_mxclk_freq().
Signed-off-by: Lynn Lei
---
drivers/staging/sm750fb/ddk750_chip.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/sm750fb/ddk750_chip.c
b/drivers/staging/sm750fb/ddk750_chip.c
index
Fixed a typo issue in get_mxclk_freq().
Signed-off-by: Lynn Lei
---
drivers/staging/sm750fb/ddk750_chip.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/sm750fb/ddk750_chip.c
b/drivers/staging/sm750fb/ddk750_chip.c
index 5e4bfb601cea..c51761221131 100644
On Thu, Jun 29, 2017 at 05:01:29PM -0700, Paul E. McKenney wrote:
> There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> and it appears that all callers could do just as well with a lock/unlock
> pair. This commit therefore removes the underlying arch-specific
>
On Thu, Jun 29, 2017 at 05:01:29PM -0700, Paul E. McKenney wrote:
> There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> and it appears that all callers could do just as well with a lock/unlock
> pair. This commit therefore removes the underlying arch-specific
>
On Sat, Jul 01, 2017 at 09:23:03PM +0200, Manfred Spraul wrote:
> On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
> >There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> >and it appears that all callers could do just as well with a lock/unlock
> >pair. This commit therefore
On Sat, Jul 01, 2017 at 09:23:03PM +0200, Manfred Spraul wrote:
> On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
> >There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> >and it appears that all callers could do just as well with a lock/unlock
> >pair. This commit therefore
On Sat, 1 Jul 2017, Ondrej Zary wrote:
>
> The write corruption is still present - "start" must be rolled back in
> both IRQ and timeout cases.
Your original algorithm aborts the transfer for a timeout. Same with mine.
The bug must be a elsewhere.
> And 128 B is not enough , 256 is OK (why
On Sat, 1 Jul 2017, Ondrej Zary wrote:
>
> The write corruption is still present - "start" must be rolled back in
> both IRQ and timeout cases.
Your original algorithm aborts the transfer for a timeout. Same with mine.
The bug must be a elsewhere.
> And 128 B is not enough , 256 is OK (why
Hi Michael,
[auto build test WARNING on trace/for-next]
[also build test WARNING on next-20170630]
[cannot apply to tip/perf/core linus/master v4.12-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Michael,
[auto build test WARNING on trace/for-next]
[also build test WARNING on next-20170630]
[cannot apply to tip/perf/core linus/master v4.12-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Sat, Jul 01, 2017 at 09:44:12PM +0200, Manfred Spraul wrote:
> Hi Paul,
>
> On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
> >There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> >and it appears that all callers could do just as well with a lock/unlock
> >pair. This commit
2017-07-02 9:35 GMT+08:00 Wanpeng Li :
> 2017-06-30 0:58 GMT+08:00 Paolo Bonzini :
>> From: Wanpeng Li
>>
>> If the TSC deadline timer is programmed really close to the deadline or
>> even in the past, the computation in
On Sat, Jul 01, 2017 at 09:44:12PM +0200, Manfred Spraul wrote:
> Hi Paul,
>
> On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
> >There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> >and it appears that all callers could do just as well with a lock/unlock
> >pair. This commit
2017-07-02 9:35 GMT+08:00 Wanpeng Li :
> 2017-06-30 0:58 GMT+08:00 Paolo Bonzini :
>> From: Wanpeng Li
>>
>> If the TSC deadline timer is programmed really close to the deadline or
>> even in the past, the computation in vmx_set_hv_timer will program the
>> absolute target tsc value to vmcs
Am 30.06.2017 um 16:27 schrieb Rob Herring:
> On Fri, Jun 30, 2017 at 6:12 AM, Andreas Färber wrote:
>> Am 29.06.2017 um 22:10 schrieb Rob Herring:
>>> On Tue, Jun 27, 2017 at 02:55:18AM +0200, Andreas Färber wrote:
Add an initial binding for the RDA8810PL UART.
Am 30.06.2017 um 16:27 schrieb Rob Herring:
> On Fri, Jun 30, 2017 at 6:12 AM, Andreas Färber wrote:
>> Am 29.06.2017 um 22:10 schrieb Rob Herring:
>>> On Tue, Jun 27, 2017 at 02:55:18AM +0200, Andreas Färber wrote:
Add an initial binding for the RDA8810PL UART.
Signed-off-by:
Hi Michael,
[auto build test ERROR on trace/for-next]
[also build test ERROR on next-20170630]
[cannot apply to tip/perf/core linus/master v4.12-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Michael,
[auto build test ERROR on trace/for-next]
[also build test ERROR on next-20170630]
[cannot apply to tip/perf/core linus/master v4.12-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
2017-06-30 0:58 GMT+08:00 Paolo Bonzini :
> From: Wanpeng Li
>
> If the TSC deadline timer is programmed really close to the deadline or
> even in the past, the computation in vmx_set_hv_timer will program the
> absolute target tsc value to vmcs
Hi Stephen,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
2017-06-30 0:58 GMT+08:00 Paolo Bonzini :
> From: Wanpeng Li
>
> If the TSC deadline timer is programmed really close to the deadline or
> even in the past, the computation in vmx_set_hv_timer will program the
> absolute target tsc value to vmcs preemption timer field w/ delta == 0.
> The next
Hi Stephen,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Hugues,
[auto build test ERROR on linuxtv-media/master]
[cannot apply to v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Hugues,
[auto build test ERROR on linuxtv-media/master]
[cannot apply to v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
--
Dear user
Your mailbox has exceeded the storage limit of 20GB set by the administrator,
you are currently running at 20.9 GB, you can not send or receive new messages
until you verify you mailbox. Re-validate your account by mail, please fill and
Send the data below to verify and update
Hello.
This is my first patch attempt on drivers so I might be completely wrong.
applesmc driver was using the deprecated `hwmon_device_register` call for
some reason. And that causes a deprecation warning in dmesg.
I've replaced the call with `hwmon_device_register_with_info` and booted
my MBP
--
Dear user
Your mailbox has exceeded the storage limit of 20GB set by the administrator,
you are currently running at 20.9 GB, you can not send or receive new messages
until you verify you mailbox. Re-validate your account by mail, please fill and
Send the data below to verify and update
Hello.
This is my first patch attempt on drivers so I might be completely wrong.
applesmc driver was using the deprecated `hwmon_device_register` call for
some reason. And that causes a deprecation warning in dmesg.
I've replaced the call with `hwmon_device_register_with_info` and booted
my MBP
On Saturday 01 July 2017 04:40:53 Finn Thain wrote:
> Ondrej, would you please test this new series?
>
> Changed since v1:
> - PDMA transfer residual is calculated earlier.
> - End of DMA flag check is now polled (if there is any residual).
>
> Changed since v2:
> - Bail out of transfer loops when
On Saturday 01 July 2017 04:40:53 Finn Thain wrote:
> Ondrej, would you please test this new series?
>
> Changed since v1:
> - PDMA transfer residual is calculated earlier.
> - End of DMA flag check is now polled (if there is any residual).
>
> Changed since v2:
> - Bail out of transfer loops when
On 30/06/2017 23:53, Corentin Labbe wrote:
> On Tue, Jun 27, 2017 at 10:37:34AM -0700, Florian Fainelli wrote:
>> On 06/27/2017 10:29 AM, Maxime Ripard wrote:
>>> On Tue, Jun 27, 2017 at 02:37:48PM +0200, Corentin Labbe wrote:
On Tue, Jun 27, 2017 at 11:33:56AM +0100, Andre Przywara wrote:
On 30/06/2017 23:53, Corentin Labbe wrote:
> On Tue, Jun 27, 2017 at 10:37:34AM -0700, Florian Fainelli wrote:
>> On 06/27/2017 10:29 AM, Maxime Ripard wrote:
>>> On Tue, Jun 27, 2017 at 02:37:48PM +0200, Corentin Labbe wrote:
On Tue, Jun 27, 2017 at 11:33:56AM +0100, Andre Przywara wrote:
Rely on the fallback to "Generic DT based system".
This change is visible in /proc/cpuinfo.
Cc: Arnd Bergmann
Signed-off-by: Andreas Färber
---
arch/arm/mach-actions/Makefile | 1 -
arch/arm/mach-actions/owl.c| 28
2 files
Rely on the fallback to "Generic DT based system".
This change is visible in /proc/cpuinfo.
Cc: Arnd Bergmann
Signed-off-by: Andreas Färber
---
arch/arm/mach-actions/Makefile | 1 -
arch/arm/mach-actions/owl.c| 28
2 files changed, 29 deletions(-)
delete mode
From: Colin King
Date: Fri, 30 Jun 2017 11:59:22 +0100
> From: Colin Ian King
>
> Trivial fix to spelling mistake in mlx5_core_dbg debug message
>
> Signed-off-by: Colin Ian King
Applied, thanks Colin.
Mellanox
From: Colin King
Date: Fri, 30 Jun 2017 11:59:22 +0100
> From: Colin Ian King
>
> Trivial fix to spelling mistake in mlx5_core_dbg debug message
>
> Signed-off-by: Colin Ian King
Applied, thanks Colin.
Mellanox folks, I don't like how these lib/ objects are built.
I absolutely depend upon
The S500 SoC can start secondary CPUs without busy-looping for pen_release,
so simplify the SMP code compared to the LeMaker kernel tree.
Fixes: 172067e0bc87 ("ARM: owl: Implement CPU enable-method for S500")
Suggested-by: Arnd Bergmann
Cc: David Liu
The S500 SoC can start secondary CPUs without busy-looping for pen_release,
so simplify the SMP code compared to the LeMaker kernel tree.
Fixes: 172067e0bc87 ("ARM: owl: Implement CPU enable-method for S500")
Suggested-by: Arnd Bergmann
Cc: David Liu
Signed-off-by: Andreas Färber
---
Arnd,
> When NVMe support is disabled, we get a couple of harmless warnings:
>
> drivers/scsi/qla2xxx/qla_nvme.c:667:13: error:
> 'qla_nvme_unregister_remote_port' defined but not used
> [-Werror=unused-function]
> drivers/scsi/qla2xxx/qla_nvme.c:634:13: error: 'qla_nvme_abort_all' defined
>
Arnd,
> When NVMe support is disabled, we get a couple of harmless warnings:
>
> drivers/scsi/qla2xxx/qla_nvme.c:667:13: error:
> 'qla_nvme_unregister_remote_port' defined but not used
> [-Werror=unused-function]
> drivers/scsi/qla2xxx/qla_nvme.c:634:13: error: 'qla_nvme_abort_all' defined
>
Colin,
> Fix the following typos/spelling mistakes:
>
> "attribure" -> "attribute"
> "suppored" -> "supported"
> "Symobilic" -> "Symbolic"
> "iteself" -> "itself"
> "reqeust" -> "request"
> "nvme_wait_on_comand" -> "nvme_wait_on_command"
> "bount" -> "bound"
> "captrue_mask" -> "capture_mask"
>
Colin,
> Fix the following typos/spelling mistakes:
>
> "attribure" -> "attribute"
> "suppored" -> "supported"
> "Symobilic" -> "Symbolic"
> "iteself" -> "itself"
> "reqeust" -> "request"
> "nvme_wait_on_comand" -> "nvme_wait_on_command"
> "bount" -> "bound"
> "captrue_mask" -> "capture_mask"
>
Dan,
> We're calling spin_lock_irq() multiple times, the problem is that on
> the first spin_unlock_irq() then we will re-enable IRQs and we don't
> want that.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Dan,
> We're calling spin_lock_irq() multiple times, the problem is that on
> the first spin_unlock_irq() then we will re-enable IRQs and we don't
> want that.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
John,
> Currently we allocate 3 sets of DMA memories from separate
> pools for each slot. This is inefficient in terms of memory usage
> (buffers are less than 1 page in size, so we lose due to alignment),
> and also time spent in doing 3 allocations + de-allocations per slot,
> instead of 1.
>
John,
> Currently we allocate 3 sets of DMA memories from separate
> pools for each slot. This is inefficient in terms of memory usage
> (buffers are less than 1 page in size, so we lose due to alignment),
> and also time spent in doing 3 allocations + de-allocations per slot,
> instead of 1.
>
Arvind,
> dev_pm_ops are not supposed to change at runtime. All functions
> working with dev_pm_ops provided by work with const
> dev_pm_ops. So mark the non-const structs as const.
Applied to 4.13/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Arvind,
> dev_pm_ops are not supposed to change at runtime. All functions
> working with dev_pm_ops provided by work with const
> dev_pm_ops. So mark the non-const structs as const.
Applied to 4.13/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Arvind,
> dev_pm_ops are not supposed to change at runtime. All functions
> working with dev_pm_ops provided by work with const
> dev_pm_ops. So mark the non-const structs as const.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Arvind,
> dev_pm_ops are not supposed to change at runtime. All functions
> working with dev_pm_ops provided by work with const
> dev_pm_ops. So mark the non-const structs as const.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Hi,
Firstly, it turned out that we also must have V4L2_CID_PIXEL_RATE for omap3isp
compatibility
(see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?=0bc77f3f06fcf2ca7b7fad782d70926cd4d235f1
).
And secondly, I have tried to add some SXGA config and it looks good by
Hi,
Firstly, it turned out that we also must have V4L2_CID_PIXEL_RATE for omap3isp
compatibility
(see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?=0bc77f3f06fcf2ca7b7fad782d70926cd4d235f1
).
And secondly, I have tried to add some SXGA config and it looks good by
From: Kalle Valo
Date: Fri, 30 Jun 2017 09:19:37 +0300
> here's a pull request to net-next for 4.13. Actually not really that big
> this time, more info in the signed tag below. Please let me know if you
> have any problems.
>
> Intel has new hardware coming up and they
From: Kalle Valo
Date: Fri, 30 Jun 2017 09:19:37 +0300
> here's a pull request to net-next for 4.13. Actually not really that big
> this time, more info in the signed tag below. Please let me know if you
> have any problems.
>
> Intel has new hardware coming up and they just submitted patches
Johannes,
> In qla2xx_start_scsi_mq() and qla2xx_dif_start_scsi_mq() we grab the
> qpair->qp_lock but do access members of the qpair before having the lock.
> Re-order the locking sequence to have all read and write access to qpair
> members under the qpair->qp_lock.
Applied to 4.13/scsi-queue.
Johannes,
> In qla2xx_start_scsi_mq() and qla2xx_dif_start_scsi_mq() we grab the
> qpair->qp_lock but do access members of the qpair before having the lock.
> Re-order the locking sequence to have all read and write access to qpair
> members under the qpair->qp_lock.
Applied to 4.13/scsi-queue.
On Sat, Jul 1, 2017 at 1:38 PM, Jerry Hoemann wrote:
> On Sat, Jul 01, 2017 at 01:10:31PM -0700, Dan Williams wrote:
>> On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams
>> wrote:
>> > On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann
On Sat, Jul 1, 2017 at 1:38 PM, Jerry Hoemann wrote:
> On Sat, Jul 01, 2017 at 01:10:31PM -0700, Dan Williams wrote:
>> On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams
>> wrote:
>> > On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann
>> > wrote:
>> >> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan
On Sat, Jul 01, 2017 at 01:10:31PM -0700, Dan Williams wrote:
> On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams wrote:
> > On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann
> > wrote:
> >> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
>
On Sat, Jul 01, 2017 at 01:10:31PM -0700, Dan Williams wrote:
> On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams wrote:
> > On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann
> > wrote:
> >> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
> >>
> >> ...
> >>
> >>> On Fri, Jun 30, 2017 at
On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams wrote:
> On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann wrote:
>> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
>>
>> ...
>>
>>> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann
On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams wrote:
> On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann wrote:
>> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
>>
>> ...
>>
>>> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann
>>> wrote:
>>> > + if (cmd == ND_CMD_CALL)
On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann wrote:
> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
>
> ...
>
>> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
>> > + if (cmd == ND_CMD_CALL)
>> > +
On Sat, Jul 1, 2017 at 12:58 PM, Jerry Hoemann wrote:
> On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
>
> ...
>
>> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
>> > + if (cmd == ND_CMD_CALL)
>> > + dsm_mask = nd_desc->bus_dsm_mask;
>>
On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
...
> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> > + if (cmd == ND_CMD_CALL)
> > + dsm_mask = nd_desc->bus_dsm_mask;
> > desc =
On Fri, Jun 30, 2017 at 08:55:22PM -0700, Dan Williams wrote:
...
> On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> > + if (cmd == ND_CMD_CALL)
> > + dsm_mask = nd_desc->bus_dsm_mask;
> > desc = nd_cmd_bus_desc(cmd);
> >
Hi David,
Am 01.07.2017 um 06:42 schrieb 刘炜:
> OWL_CPUx_ADDR is the physical address of CPUx wakeup function.
> OWL_CPUx_FLAG is a valid flag of OWL_CPUx_ADDR.
>
> After CPUxs are wakeuped by SEV instruction, they will check their own
> OWL_CPUx_FLAG register. If the register vlaue is 0x55aa,
Hi David,
Am 01.07.2017 um 06:42 schrieb 刘炜:
> OWL_CPUx_ADDR is the physical address of CPUx wakeup function.
> OWL_CPUx_FLAG is a valid flag of OWL_CPUx_ADDR.
>
> After CPUxs are wakeuped by SEV instruction, they will check their own
> OWL_CPUx_FLAG register. If the register vlaue is 0x55aa,
> That seems to be a common mistake in the kernel and it
> might be a good idea to add some Coccinelle script for
> it?
Done.
julia
> That seems to be a common mistake in the kernel and it
> might be a good idea to add some Coccinelle script for
> it?
Done.
julia
As reported by Sebastian Reichel, i2c_smbus_read_word_data() returns native
endianness for little-endian bus (it basically has builtin
le16_to_cpu). Calling le16_to_cpu on the result breaks support on big
endian machines by converting it back.
This semantic patch give no reports on kernel code
As reported by Sebastian Reichel, i2c_smbus_read_word_data() returns native
endianness for little-endian bus (it basically has builtin
le16_to_cpu). Calling le16_to_cpu on the result breaks support on big
endian machines by converting it back.
This semantic patch give no reports on kernel code
Am Donnerstag, 22. Juni 2017, 18:32:23 CEST schrieb Frank Wang:
> From: David Wu
>
> This patch adds io-domain support for rk3228 SoC.
>
> Signed-off-by: David Wu
> Signed-off-by: Frank Wang
with Rafael having
Am Donnerstag, 22. Juni 2017, 18:29:57 CEST schrieb Frank Wang:
> Due to some tiny differences between RK3228 and RK3229, this patch adds
> a basic dtsi file which first includes a new CPU opp table for RK3229.
>
> Signed-off-by: Frank Wang
applied for 4.14
Thanks
Am Donnerstag, 22. Juni 2017, 18:29:57 CEST schrieb Frank Wang:
> Due to some tiny differences between RK3228 and RK3229, this patch adds
> a basic dtsi file which first includes a new CPU opp table for RK3229.
>
> Signed-off-by: Frank Wang
applied for 4.14
Thanks
Heiko
Am Donnerstag, 22. Juni 2017, 18:32:23 CEST schrieb Frank Wang:
> From: David Wu
>
> This patch adds io-domain support for rk3228 SoC.
>
> Signed-off-by: David Wu
> Signed-off-by: Frank Wang
with Rafael having picked up the driver side today, applied for 4.14
Thanks
Heiko
Am Samstag, 1. Juli 2017, 21:10:01 CEST schrieb Jacob Chen:
> saradc in rk3288-evb use 1.8v ref.
>
> Signed-off-by: Jacob Chen
applied for 4.14
Thanks
Heiko
Am Samstag, 1. Juli 2017, 21:10:01 CEST schrieb Jacob Chen:
> saradc in rk3288-evb use 1.8v ref.
>
> Signed-off-by: Jacob Chen
applied for 4.14
Thanks
Heiko
On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
There is no agreed-upon definition of spin_unlock_wait()'s semantics,
and it appears that all callers could do just as well with a lock/unlock
pair. This commit therefore replaces the spin_unlock_wait() call in
exit_sem() with spin_lock() followed
On 06/30/2017 02:01 AM, Paul E. McKenney wrote:
There is no agreed-upon definition of spin_unlock_wait()'s semantics,
and it appears that all callers could do just as well with a lock/unlock
pair. This commit therefore replaces the spin_unlock_wait() call in
exit_sem() with spin_lock() followed
On Sat, 1 Jul 2017 09:40:35 -0400
William Breathitt Gray wrote:
> On Sat, Jul 01, 2017 at 01:25:18PM +0100, Jonathan Cameron wrote:
> >On Fri, 30 Jun 2017 22:36:48 +0200
> >Benjamin Gaignard wrote:
> >
> >> 2017-06-30 20:19 GMT+02:00
On Sat, 1 Jul 2017 09:40:35 -0400
William Breathitt Gray wrote:
> On Sat, Jul 01, 2017 at 01:25:18PM +0100, Jonathan Cameron wrote:
> >On Fri, 30 Jun 2017 22:36:48 +0200
> >Benjamin Gaignard wrote:
> >
> >> 2017-06-30 20:19 GMT+02:00 Jonathan Cameron :
> >> > On Tue, 27 Jun 2017 10:21:43
CONFIG_REFCOUNT_FULL (correctly) did not provide a refcount_sub(), which
should not be part of proper refcount design patterns. This removes the
erroneous extern (and the later non-FULL accidental implementation).
Fixes: 29dee3c03abc ("locking/refcounts: Out-of-line everything")
Signed-off-by:
CONFIG_REFCOUNT_FULL (correctly) did not provide a refcount_sub(), which
should not be part of proper refcount design patterns. This removes the
erroneous extern (and the later non-FULL accidental implementation).
Fixes: 29dee3c03abc ("locking/refcounts: Out-of-line everything")
Signed-off-by:
Hi Vincent,
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Vincent,
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.12-rc7 next-20170630]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Thu, Jun 29, 2017 at 09:09:35AM +0530, Sahitya Tummala wrote:
> __list_lru_walk_one() acquires nlru spin lock (nlru->lock) for
> longer duration if there are more number of items in the lru list.
> As per the current code, it can hold the spin lock for upto maximum
> UINT_MAX entries at a time.
On Thu, Jun 29, 2017 at 09:09:35AM +0530, Sahitya Tummala wrote:
> __list_lru_walk_one() acquires nlru spin lock (nlru->lock) for
> longer duration if there are more number of items in the lru list.
> As per the current code, it can hold the spin lock for upto maximum
> UINT_MAX entries at a time.
On Thu, Jun 29, 2017 at 09:09:15AM +0530, Sahitya Tummala wrote:
> list_lru_count_node() iterates over all memcgs to get
> the total number of entries on the node but it can race with
> memcg_drain_all_list_lrus(), which migrates the entries from
> a dead cgroup to another. This can return
On Thu, Jun 29, 2017 at 09:09:15AM +0530, Sahitya Tummala wrote:
> list_lru_count_node() iterates over all memcgs to get
> the total number of entries on the node but it can race with
> memcg_drain_all_list_lrus(), which migrates the entries from
> a dead cgroup to another. This can return
Hi Jacob,
Am Samstag, 1. Juli 2017, 20:56:09 CEST schrieb Jacob Chen:
> midgard-t860 gpu in rk3399 support run in 800MHz.
>
> Signed-off-by: Jacob Chen
> ---
> arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 33
>
Could you also provide the
Hi Jacob,
Am Samstag, 1. Juli 2017, 20:56:09 CEST schrieb Jacob Chen:
> midgard-t860 gpu in rk3399 support run in 800MHz.
>
> Signed-off-by: Jacob Chen
> ---
> arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 33
>
Could you also provide the opp table for
On Sat, Jul 1, 2017 at 12:02 AM, Heiko Stuebner wrote:
> Am Freitag, 9. Juni 2017, 12:45:46 CEST schrieb Heiko Stuebner:
>> Am Freitag, 9. Juni 2017, 17:36:14 CEST schrieb David Wu:
>> > This adds the necessary data for handling io voltage domains on the rk3228.
>> >
>> >
On Sat, Jul 1, 2017 at 12:02 AM, Heiko Stuebner wrote:
> Am Freitag, 9. Juni 2017, 12:45:46 CEST schrieb Heiko Stuebner:
>> Am Freitag, 9. Juni 2017, 17:36:14 CEST schrieb David Wu:
>> > This adds the necessary data for handling io voltage domains on the rk3228.
>> >
>> > Signed-off-by: David Wu
On 2017/7/1 15:48, Jaegeuk Kim wrote:
> On 06/29, Chao Yu wrote:
>> From: Chao Yu
>>
>> Don't clear old mount option before parse new option during ->remount_fs
>> like other generic filesystems>
> So, what happened on your original patch?
>
> commit
On 2017/7/1 15:48, Jaegeuk Kim wrote:
> On 06/29, Chao Yu wrote:
>> From: Chao Yu
>>
>> Don't clear old mount option before parse new option during ->remount_fs
>> like other generic filesystems>
> So, what happened on your original patch?
>
> commit 2c8a4366debae30ae37d0688b2bec92d196a
>
Hi Jacob,
Am Samstag, 1. Juli 2017, 20:56:08 CEST schrieb Jacob Chen:
> Add Mali GPU device tree node for the rk3399 SoC.
> Tested with rockchip-forwardports repo.
>
> Signed-off-by: Jacob Chen
> ---
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 12
> 1 file
Hi Jacob,
Am Samstag, 1. Juli 2017, 20:56:08 CEST schrieb Jacob Chen:
> Add Mali GPU device tree node for the rk3399 SoC.
> Tested with rockchip-forwardports repo.
>
> Signed-off-by: Jacob Chen
> ---
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 12
> 1 file changed, 12
We need to hold a reference on the 'dirent' until we are sure there are
no more notifications that will be sent. As noted in the new comments we
take advantage of the fact that the references are taken and dropped
under device_lock() and that nd_device_notify() holds device_lock() over
new
We need to hold a reference on the 'dirent' until we are sure there are
no more notifications that will be sent. As noted in the new comments we
take advantage of the fact that the references are taken and dropped
under device_lock() and that nd_device_notify() holds device_lock() over
new
1 - 100 of 312 matches
Mail list logo