Removed unnecessary error message as appropriate error code is returned.
Changed error message into a debug.
Signed-off-by: Shuah Khan
---
Changes since v1:
- Changed EBUSY error message to a debug message.
drivers/media/platform/s5p-mfc/s5p_mfc.c | 3 +--
1 file
Removed unnecessary error message as appropriate error code is returned.
Changed error message into a debug.
Signed-off-by: Shuah Khan
---
Changes since v1:
- Changed EBUSY error message to a debug message.
drivers/media/platform/s5p-mfc/s5p_mfc.c | 3 +--
1 file changed, 1 insertion(+), 2
On Thu 14-07-16 16:33:38, Rafael J. Wysocki wrote:
> On Thursday, July 14, 2016 04:12:16 PM Jan Kara wrote:
> > On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> > > Cc Petr Mladek.
> > >
> > > On (07/12/16 16:19), Viresh Kumar wrote:
> > > [..]
> > > > Okay, we have tracked this BUG and its
On Thu 14-07-16 16:33:38, Rafael J. Wysocki wrote:
> On Thursday, July 14, 2016 04:12:16 PM Jan Kara wrote:
> > On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> > > Cc Petr Mladek.
> > >
> > > On (07/12/16 16:19), Viresh Kumar wrote:
> > > [..]
> > > > Okay, we have tracked this BUG and its
On Tuesday, July 12, 2016 11:18:39 AM CEST Michael Turquette wrote:
> Quoting Arnd Bergmann (2016-07-12 01:51:36)
> > On Monday, July 11, 2016 3:00:13 PM CEST Michael Turquette wrote:
> > > Quoting Arnd Bergmann (2016-07-11 13:21:17)
> > > > On Thursday, July 7, 2016 7:10:30 PM CEST Michael
On Tuesday, July 12, 2016 11:18:39 AM CEST Michael Turquette wrote:
> Quoting Arnd Bergmann (2016-07-12 01:51:36)
> > On Monday, July 11, 2016 3:00:13 PM CEST Michael Turquette wrote:
> > > Quoting Arnd Bergmann (2016-07-11 13:21:17)
> > > > On Thursday, July 7, 2016 7:10:30 PM CEST Michael
Hello Jan,
On (07/14/16 16:12), Jan Kara wrote:
[..]
> > *** a printk() call from here will kill the system. either it will
> > recurse printk(), or spin forever in 'nested' printk() on one of
> > the already taken spin locks.
[..]
> And with sync printk the above deadlock doesn't trigger only by
Hello Jan,
On (07/14/16 16:12), Jan Kara wrote:
[..]
> > *** a printk() call from here will kill the system. either it will
> > recurse printk(), or spin forever in 'nested' printk() on one of
> > the already taken spin locks.
[..]
> And with sync printk the above deadlock doesn't trigger only by
On Thu, 14 Jul 2016, Michal Hocko wrote:
> On Wed 13-07-16 11:02:15, Mikulas Patocka wrote:
> > > diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> > > index 4f3cb3554944..0b806810efab 100644
> > > --- a/drivers/md/dm-crypt.c
> > > +++ b/drivers/md/dm-crypt.c
> > > @@ -1392,11
On Thu, 14 Jul 2016, Michal Hocko wrote:
> On Wed 13-07-16 11:02:15, Mikulas Patocka wrote:
> > > diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> > > index 4f3cb3554944..0b806810efab 100644
> > > --- a/drivers/md/dm-crypt.c
> > > +++ b/drivers/md/dm-crypt.c
> > > @@ -1392,11
On 07/13/2016 11:13 AM, Vivek Goyal wrote:
> Updated patch as per Stephen's feedback.
>
> Provide a security hook to label new file correctly when a file is copied
> up from lower layer to upper layer of a overlay/union mount.
>
> This hook can prepare a new set of creds which are suitable for
On 07/13/2016 11:13 AM, Vivek Goyal wrote:
> Updated patch as per Stephen's feedback.
>
> Provide a security hook to label new file correctly when a file is copied
> up from lower layer to upper layer of a overlay/union mount.
>
> This hook can prepare a new set of creds which are suitable for
On Thursday, July 14, 2016 04:12:16 PM Jan Kara wrote:
> On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> > Cc Petr Mladek.
> >
> > On (07/12/16 16:19), Viresh Kumar wrote:
> > [..]
> > > Okay, we have tracked this BUG and its really interesting.
> >
> > good find!
> >
> > > I hacked the
On Thursday, July 14, 2016 04:12:16 PM Jan Kara wrote:
> On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> > Cc Petr Mladek.
> >
> > On (07/12/16 16:19), Viresh Kumar wrote:
> > [..]
> > > Okay, we have tracked this BUG and its really interesting.
> >
> > good find!
> >
> > > I hacked the
On 07/13/2016 10:44 AM, Vivek Goyal wrote:
> During a new file creation we need to make sure new file is created with the
> right label. New file is created in upper/ so effectively file should get
> label as if task had created file in upper/.
>
> We switched to mounter's creds for actual file
On 07/13/2016 10:44 AM, Vivek Goyal wrote:
> During a new file creation we need to make sure new file is created with the
> right label. New file is created in upper/ so effectively file should get
> label as if task had created file in upper/.
>
> We switched to mounter's creds for actual file
On 07/14/2016 06:47 AM, Vlastimil Babka wrote:
> So, this might be just because I know next to nothing about (para)virt,
> but...
>
> in arch/x86/include/asm/paravirt.h, pte_val is implemented via some
> pvops, which suggests that obtaining a pte value is different than just
> reading it from
On 07/14/2016 06:47 AM, Vlastimil Babka wrote:
> So, this might be just because I know next to nothing about (para)virt,
> but...
>
> in arch/x86/include/asm/paravirt.h, pte_val is implemented via some
> pvops, which suggests that obtaining a pte value is different than just
> reading it from
On 7/13/16, 9:28 PM, "Martin K. Petersen" wrote:
>> "Johannes" == Johannes Thumshirn writes:
>
>Johannes> qla2xxx first calls request_irq() and then does the setup of
>Johannes> the queue entry data needed in the interrupt handlers in when
On 7/13/16, 9:28 PM, "Martin K. Petersen" wrote:
>> "Johannes" == Johannes Thumshirn writes:
>
>Johannes> qla2xxx first calls request_irq() and then does the setup of
>Johannes> the queue entry data needed in the interrupt handlers in when
>Johannes> using MSI-X. This could lead to a NULL
On 07/13/2016 10:44 AM, Vivek Goyal wrote:
> Provide a security hook which is called when xattrs of a file are being
> copied up. This hook is called once for each xattr and LSM can return
> 0 if the security module wants the xattr to be copied up, 1 if the
> security module wants the xattr to be
On 07/13/2016 10:44 AM, Vivek Goyal wrote:
> Provide a security hook which is called when xattrs of a file are being
> copied up. This hook is called once for each xattr and LSM can return
> 0 if the security module wants the xattr to be copied up, 1 if the
> security module wants the xattr to be
[ added CCs ]
On Tue, 12 Jul 2016, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on net/master]
> [also build test ERROR on v4.7-rc7 next-20160711]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
>
On Thu, Jul 14, 2016 at 03:18:09PM +0200, Peter Zijlstra wrote:
> On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote:
> > So, IIRC, the trade-off is a full memory barrier in read_lock and
> > read_unlock() vs sync_sched() in write.
> >
> > Full memory barriers are expensive and while
[ added CCs ]
On Tue, 12 Jul 2016, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on net/master]
> [also build test ERROR on v4.7-rc7 next-20160711]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
>
On Thu, Jul 14, 2016 at 03:18:09PM +0200, Peter Zijlstra wrote:
> On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote:
> > So, IIRC, the trade-off is a full memory barrier in read_lock and
> > read_unlock() vs sync_sched() in write.
> >
> > Full memory barriers are expensive and while
On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> Cc Petr Mladek.
>
> On (07/12/16 16:19), Viresh Kumar wrote:
> [..]
> > Okay, we have tracked this BUG and its really interesting.
>
> good find!
>
> > I hacked the platform's serial driver to implement a putchar() routine
> > that simply
On Wed 13-07-16 14:45:07, Sergey Senozhatsky wrote:
> Cc Petr Mladek.
>
> On (07/12/16 16:19), Viresh Kumar wrote:
> [..]
> > Okay, we have tracked this BUG and its really interesting.
>
> good find!
>
> > I hacked the platform's serial driver to implement a putchar() routine
> > that simply
On Wed, 13 Jul 2016, Rafał Miłecki wrote:
> Probing function was using >dev and dev->dev.of_node over 20 times
> so I believe it made sense to use helper variables for both of them.
> To avoid some uncommon variable name for struct device I first replaced
> existing dev variable with pdev.
>
>
On Wed, 13 Jul 2016, Rafał Miłecki wrote:
> Probing function was using >dev and dev->dev.of_node over 20 times
> so I believe it made sense to use helper variables for both of them.
> To avoid some uncommon variable name for struct device I first replaced
> existing dev variable with pdev.
>
>
On Wed, Jul 13, 2016 at 8:08 PM, Chris Zhong wrote:
> Hi Sean
>
> Thanks for your detailed review. I'm working to modify most of code
> according to comment.
> And there is reply for some comment
>
> On 07/13/2016 09:59 PM, Sean Paul wrote:
>>
>> On Tue, Jul 12, 2016 at 8:09
On Wed, Jul 13, 2016 at 8:08 PM, Chris Zhong wrote:
> Hi Sean
>
> Thanks for your detailed review. I'm working to modify most of code
> according to comment.
> And there is reply for some comment
>
> On 07/13/2016 09:59 PM, Sean Paul wrote:
>>
>> On Tue, Jul 12, 2016 at 8:09 AM, Chris Zhong
On Tuesday, July 12, 2016 4:05:41 PM CEST Patrice Chotard wrote:
> Highlights:
> ---
> - Add STi DT critical clocks declaration
> - Remove SPI hack wich has dependecy with critical clocks
>
> These 2 STi DT patches and SPI hack MUST be applied after patches
> contained into Stephen Boyd's
On Tuesday, July 12, 2016 4:05:41 PM CEST Patrice Chotard wrote:
> Highlights:
> ---
> - Add STi DT critical clocks declaration
> - Remove SPI hack wich has dependecy with critical clocks
>
> These 2 STi DT patches and SPI hack MUST be applied after patches
> contained into Stephen Boyd's
On Monday, July 11, 2016 6:41:18 PM CEST Krzysztof Kozlowski wrote:
> Samsung defconfig updates for ARM64 - enable drivers for
> Exynos7 and Exynos5433 based boards:
> 1. S2MPS clock driver,
> 2. SoC: RTC, SPI, watchdog, EHCI, OHCI, DWC3, ADC and PWM,
> 3. Enable Samsung SoC sound.
>
Merged into
On Monday, July 11, 2016 6:41:18 PM CEST Krzysztof Kozlowski wrote:
> Samsung defconfig updates for ARM64 - enable drivers for
> Exynos7 and Exynos5433 based boards:
> 1. S2MPS clock driver,
> 2. SoC: RTC, SPI, watchdog, EHCI, OHCI, DWC3, ADC and PWM,
> 3. Enable Samsung SoC sound.
>
Merged into
radix_tree_iter_retry() resets slot to NULL, but it doesn't reset tags.
Then NULL slot and non-zero iter.tags passed to radix_tree_next_slot()
leading to crash:
RIP: [< inline >] radix_tree_next_slot include/linux/radix-tree.h:473
[] find_get_pages_tag+0x334/0x930 mm/filemap.c:1452
radix_tree_iter_retry() resets slot to NULL, but it doesn't reset tags.
Then NULL slot and non-zero iter.tags passed to radix_tree_next_slot()
leading to crash:
RIP: [< inline >] radix_tree_next_slot include/linux/radix-tree.h:473
[] find_get_pages_tag+0x334/0x930 mm/filemap.c:1452
On 07/08/2016 02:19 AM, Dave Hansen wrote:
From: Dave Hansen
The page table manipulation code seems to have grown a couple of
sites that are looking for empty PTEs. Just in case one of these
entries got a stray bit set, use pte_none() instead of checking
for a
On 07/08/2016 02:19 AM, Dave Hansen wrote:
From: Dave Hansen
The page table manipulation code seems to have grown a couple of
sites that are looking for empty PTEs. Just in case one of these
entries got a stray bit set, use pte_none() instead of checking
for a zero pte_val().
The use
Hi Wan Zongshun,
On Thu, Jul 14, 2016 at 11:36:53AM +0800, Wan Zongshun wrote:
> On 2016年07月14日 04:09, Jason Cooper wrote:
> >On Sun, Jul 10, 2016 at 03:27:22PM +0800, Wan Zongshun wrote:
> >>This patch is to add irqchip driver support for nuc900 plat,
> >>current this driver only supports nuc970
Hi Wan Zongshun,
On Thu, Jul 14, 2016 at 11:36:53AM +0800, Wan Zongshun wrote:
> On 2016年07月14日 04:09, Jason Cooper wrote:
> >On Sun, Jul 10, 2016 at 03:27:22PM +0800, Wan Zongshun wrote:
> >>This patch is to add irqchip driver support for nuc900 plat,
> >>current this driver only supports nuc970
2016-07-14 16:43+0700, Suravee Suthikulpanit:
> On 7/13/16 21:29, Radim Krčmář wrote:
>> 2016-07-13 08:20-0500, Suravee Suthikulpanit:
>> > >diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>> > >+ hash_for_each_possible(svm_vm_data_hash, ka, hnode, vm_id) {
>> > >+ struct kvm *kvm =
2016-07-14 16:43+0700, Suravee Suthikulpanit:
> On 7/13/16 21:29, Radim Krčmář wrote:
>> 2016-07-13 08:20-0500, Suravee Suthikulpanit:
>> > >diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>> > >+ hash_for_each_possible(svm_vm_data_hash, ka, hnode, vm_id) {
>> > >+ struct kvm *kvm =
2016-07-14 16:33+0700, Suravee Suthikulpanit:
> On 7/14/16 16:13, Suravee Suthikulpanit wrote:
>> > >unsigned long flags;
>> > > +struct amd_iommu *iommu;
>> > > +
>> > > +if (!AMD_IOMMU_GUEST_IR_VAPIC(amd_iommu_guest_ir))
>> > > +return 0;
>> > > +
>> > > +
2016-07-14 16:33+0700, Suravee Suthikulpanit:
> On 7/14/16 16:13, Suravee Suthikulpanit wrote:
>> > >unsigned long flags;
>> > > +struct amd_iommu *iommu;
>> > > +
>> > > +if (!AMD_IOMMU_GUEST_IR_VAPIC(amd_iommu_guest_ir))
>> > > +return 0;
>> > > +
>> > > +
On 13 July 2016 at 18:14, Morten Rasmussen wrote:
> On Wed, Jul 13, 2016 at 02:56:41PM +0200, Vincent Guittot wrote:
>> On 22 June 2016 at 19:03, Morten Rasmussen wrote:
>> > Currently, SD_WAKE_AFFINE always takes priority over wakeup balancing
On 13 July 2016 at 18:14, Morten Rasmussen wrote:
> On Wed, Jul 13, 2016 at 02:56:41PM +0200, Vincent Guittot wrote:
>> On 22 June 2016 at 19:03, Morten Rasmussen wrote:
>> > Currently, SD_WAKE_AFFINE always takes priority over wakeup balancing if
>> > SD_BALANCE_WAKE is set on the
On Monday, July 11, 2016 6:41:17 PM CEST Krzysztof Kozlowski wrote:
> Samsung DeviceTree changes for ARM64 for v4.8:
> 1. Adjust the voltage of CPU buck regulator so scaling could work.
>
>
Pulled into next/dt64, thanks!
Arnd
On Monday, July 11, 2016 6:41:17 PM CEST Krzysztof Kozlowski wrote:
> Samsung DeviceTree changes for ARM64 for v4.8:
> 1. Adjust the voltage of CPU buck regulator so scaling could work.
>
>
Pulled into next/dt64, thanks!
Arnd
Hi David,
I have found that I missed some piece of code in a patch
and also discovered a corner case issue while further testing.
Please ignore this patch set, will submit another version soon.
Thanks,
Sunil.
On Wed, Jul 13, 2016 at 11:29 AM, wrote:
> From: Sunil
Hi David,
I have found that I missed some piece of code in a patch
and also discovered a corner case issue while further testing.
Please ignore this patch set, will submit another version soon.
Thanks,
Sunil.
On Wed, Jul 13, 2016 at 11:29 AM, wrote:
> From: Sunil Goutham
>
> This patch
On Monday, July 11, 2016 6:41:16 PM CEST Krzysztof Kozlowski wrote:
> Samsung mach/soc update for v4.8, part 3:
> Just cleanup - fix Sparse warning and constify passed iomem address.
>
Pulled into next/soc, thanks!
Arnd
On Monday, July 11, 2016 6:41:16 PM CEST Krzysztof Kozlowski wrote:
> Samsung mach/soc update for v4.8, part 3:
> Just cleanup - fix Sparse warning and constify passed iomem address.
>
Pulled into next/soc, thanks!
Arnd
On 7/14/2016 5:48 AM, Serge E. Hallyn wrote:
Can someone give a detailed explanation of what you could do with
the new timerslack feature and compare it to what you can do with
sys_nice?
what you can do with the timerslack feature is add upto 4 seconds of extra
time/delay on top of each
On 7/14/2016 5:48 AM, Serge E. Hallyn wrote:
Can someone give a detailed explanation of what you could do with
the new timerslack feature and compare it to what you can do with
sys_nice?
what you can do with the timerslack feature is add upto 4 seconds of extra
time/delay on top of each
On Thu, Jul 14, 2016 at 01:53:20AM +0800, fu@linaro.org wrote:
> From: Fu Wei
>
> This driver adds support for parsing memory-mapped timer in GTDT:
> provide a kernel APIs to parse GT Block Structure in GTDT,
> export all the info by filling the struct which provided
> by
On Thu, Jul 14, 2016 at 01:53:20AM +0800, fu@linaro.org wrote:
> From: Fu Wei
>
> This driver adds support for parsing memory-mapped timer in GTDT:
> provide a kernel APIs to parse GT Block Structure in GTDT,
> export all the info by filling the struct which provided
> by parameter(pointer
Looks good. Thanks!
regards,
dan carpenter
Looks good. Thanks!
regards,
dan carpenter
2016-07-14 16:13+0700, Suravee Suthikulpanit:
> On 7/13/16 21:14, Radim Krčmář wrote:
>> 2016-07-13 08:20-0500, Suravee Suthikulpanit:
>> > diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
>> > @@ -4461,4 +4461,69 @@ int amd_iommu_create_irq_domain(struct amd_iommu
>> > *iommu)
2016-07-14 16:13+0700, Suravee Suthikulpanit:
> On 7/13/16 21:14, Radim Krčmář wrote:
>> 2016-07-13 08:20-0500, Suravee Suthikulpanit:
>> > diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
>> > @@ -4461,4 +4461,69 @@ int amd_iommu_create_irq_domain(struct amd_iommu
>> > *iommu)
On 07/08/2016 11:35 AM, Mel Gorman wrote:
The number of LRU pages, dirty pages and writeback pages must be accounted
for on both zones and nodes because of the reclaim retry logic, compaction
retry logic and highmem calculations all depending on per-zone stats.
Many lowmem allocations are
On 07/08/2016 11:35 AM, Mel Gorman wrote:
The number of LRU pages, dirty pages and writeback pages must be accounted
for on both zones and nodes because of the reclaim retry logic, compaction
retry logic and highmem calculations all depending on per-zone stats.
Many lowmem allocations are
Hello Shuah,
On 07/14/2016 09:35 AM, Shuah Khan wrote:
> On 07/14/2016 06:46 AM, Javier Martinez Canillas wrote:
>> Hello Shuah,
>>
>> On 07/12/2016 08:33 PM, Shuah Khan wrote:
>>> Removing unnecessary error messages as appropriate error code is returned.
>>>
>>> Signed-off-by: Shuah Khan
Hello Shuah,
On 07/14/2016 09:35 AM, Shuah Khan wrote:
> On 07/14/2016 06:46 AM, Javier Martinez Canillas wrote:
>> Hello Shuah,
>>
>> On 07/12/2016 08:33 PM, Shuah Khan wrote:
>>> Removing unnecessary error messages as appropriate error code is returned.
>>>
>>> Signed-off-by: Shuah Khan
>>>
On 07/14/2016 06:46 AM, Javier Martinez Canillas wrote:
> Hello Shuah,
>
> On 07/12/2016 08:33 PM, Shuah Khan wrote:
>> Removing unnecessary error messages as appropriate error code is returned.
>>
>> Signed-off-by: Shuah Khan
>> ---
>>
On 07/14/2016 06:46 AM, Javier Martinez Canillas wrote:
> Hello Shuah,
>
> On 07/12/2016 08:33 PM, Shuah Khan wrote:
>> Removing unnecessary error messages as appropriate error code is returned.
>>
>> Signed-off-by: Shuah Khan
>> ---
>> drivers/media/platform/s5p-mfc/s5p_mfc.c | 2 --
>> 1 file
> > Subject: Re: Purpose of pci_remap_iospace
> >
> > On Wed, Jul 13, 2016 at 12:30:44PM +, Bharat Kumar Gogada wrote:
> >
> > [...]
> >
> > > err = of_pci_get_host_bridge_resources(node, 0, 0xff, , );
> > > if (err) {
> > > pr_err("Getting bridge resources failed\n");
> > Subject: Re: Purpose of pci_remap_iospace
> >
> > On Wed, Jul 13, 2016 at 12:30:44PM +, Bharat Kumar Gogada wrote:
> >
> > [...]
> >
> > > err = of_pci_get_host_bridge_resources(node, 0, 0xff, , );
> > > if (err) {
> > > pr_err("Getting bridge resources failed\n");
This patch fixes the below static checker warning
drivers/dma/xilinx/zynqmp_dma.c:973 zynqmp_dma_chan_probe()
warn: was && intended here instead of ||?
Reported-by: Dan Carpenter
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
--->
This patch fixes the below static checker warning
drivers/dma/xilinx/zynqmp_dma.c:973 zynqmp_dma_chan_probe()
warn: was && intended here instead of ||?
Reported-by: Dan Carpenter
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> Return EINVAL instead of err as suggested by
On Tue, Jul 12, 2016 at 02:19:20PM -0400, Nate Watterson wrote:
> In the current arm-smmu-v3 driver, all smmus that support 2-level
> stream tables are being forced to use them. This is suboptimal for
> smmus that support fewer stream id bits than would fill in a single
> second level table. This
On Tue, Jul 12, 2016 at 02:19:20PM -0400, Nate Watterson wrote:
> In the current arm-smmu-v3 driver, all smmus that support 2-level
> stream tables are being forced to use them. This is suboptimal for
> smmus that support fewer stream id bits than would fill in a single
> second level table. This
On Wed, Jul 13, 2016 at 01:34:36PM -0600, Girish Mahadevan wrote:
> We’re working on a driver for a Quad SPI controller [using up to 4 data
> lines] which can use dual-data-sampling to implement 8-bit transfers. To
> allow a slave driver to specify the 8-bit transfer we'd like to make this
>
On Wed, Jul 13, 2016 at 01:34:36PM -0600, Girish Mahadevan wrote:
> We’re working on a driver for a Quad SPI controller [using up to 4 data
> lines] which can use dual-data-sampling to implement 8-bit transfers. To
> allow a slave driver to specify the 8-bit transfer we'd like to make this
>
On 12/07/2016 19:08, Gustavo Padovan wrote:
...
+++ b/include/linux/sync_file.h
@@ -28,6 +28,7 @@
* @name: name of sync_file. Useful for debugging
* @sync_file_list: membership in global file list
* @wq: wait queue for fence signaling
+ * @enabled:
On 12/07/2016 19:08, Gustavo Padovan wrote:
...
+++ b/include/linux/sync_file.h
@@ -28,6 +28,7 @@
* @name: name of sync_file. Useful for debugging
* @sync_file_list: membership in global file list
* @wq: wait queue for fence signaling
+ * @enabled:
Chipsets before Exynos5420 did not support HS400 so if MMC core tries to
configure HS400 timing, this might or might not work. Warn in such
cases because this is DTB misconfiguration.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mmc/host/dw_mmc-exynos.c | 6 +-
1
On 07/12, Shayan Pooya wrote:
>
> > Yep. Bug still not fixed in upstream. In our kernel I've plugged it with
> > this:
> >
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -2808,8 +2808,9 @@ asmlinkage __visible void schedule_tail(struct
> > task_struct *prev)
> >
Chipsets before Exynos5420 did not support HS400 so if MMC core tries to
configure HS400 timing, this might or might not work. Warn in such
cases because this is DTB misconfiguration.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mmc/host/dw_mmc-exynos.c | 6 +-
1 file changed, 5
On 07/12, Shayan Pooya wrote:
>
> > Yep. Bug still not fixed in upstream. In our kernel I've plugged it with
> > this:
> >
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -2808,8 +2808,9 @@ asmlinkage __visible void schedule_tail(struct
> > task_struct *prev)
> >
On Monday, July 11, 2016 6:41:15 PM CEST Krzysztof Kozlowski wrote:
> Samsung drivers/soc update for v4.8, part 3
> 1. Fix size of allocation for Exynos SROM registers (too much was allocated).
> 2. Constify fix.
>
Pulled into next/drivers, thanks!
Arnd
On Monday, July 11, 2016 6:41:15 PM CEST Krzysztof Kozlowski wrote:
> Samsung drivers/soc update for v4.8, part 3
> 1. Fix size of allocation for Exynos SROM registers (too much was allocated).
> 2. Constify fix.
>
Pulled into next/drivers, thanks!
Arnd
On 13 July 2016 at 18:37, Morten Rasmussen wrote:
> On Wed, Jul 13, 2016 at 02:48:24PM +0100, Dietmar Eggemann wrote:
>> On 13/07/16 13:40, Vincent Guittot wrote:
>> > On 22 June 2016 at 19:03, Morten Rasmussen
>> > wrote:
>> >> From: Dietmar
On 13 July 2016 at 18:37, Morten Rasmussen wrote:
> On Wed, Jul 13, 2016 at 02:48:24PM +0100, Dietmar Eggemann wrote:
>> On 13/07/16 13:40, Vincent Guittot wrote:
>> > On 22 June 2016 at 19:03, Morten Rasmussen
>> > wrote:
>> >> From: Dietmar Eggemann
>> >>
>> >> To be able to compare the
On Mon, Jul 11, 2016 at 12:05:40PM -0700, Tai Nguyen wrote:
> In addition to the X-Gene ARM CPU performance monitoring unit (PMU), there
> are PMU for the SoC system devices such as L3 cache(s), I/O bridge(s),
> memory controller bridges and memory. These PMU devices are loosely
> architected to
On Mon, Jul 11, 2016 at 12:05:40PM -0700, Tai Nguyen wrote:
> In addition to the X-Gene ARM CPU performance monitoring unit (PMU), there
> are PMU for the SoC system devices such as L3 cache(s), I/O bridge(s),
> memory controller bridges and memory. These PMU devices are loosely
> architected to
The private structure contain a pointer to phydev, but the structure
net_device already contain such pointer. So we can remove the pointer
phy in the private structure, and update the driver to use the
one contained in struct net_device.
Signed-off-by: Philippe Reynes
---
The private structure contain a pointer to phydev, but the structure
net_device already contain such pointer. So we can remove the pointer
phy in the private structure, and update the driver to use the
one contained in struct net_device.
Signed-off-by: Philippe Reynes
---
There are two generics functions phy_ethtool_{get|set}_link_ksettings,
so we can use them instead of defining the same code in the driver.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/toshiba/tc35815.c | 18 ++
1 files changed, 2 insertions(+), 16
There are two generics functions phy_ethtool_{get|set}_link_ksettings,
so we can use them instead of defining the same code in the driver.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/toshiba/tc35815.c | 18 ++
1 files changed, 2 insertions(+), 16 deletions(-)
diff
On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote:
> So, IIRC, the trade-off is a full memory barrier in read_lock and
> read_unlock() vs sync_sched() in write.
>
> Full memory barriers are expensive and while the combined cost might
> well exceed the cost of the sync_sched() it
On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote:
> So, IIRC, the trade-off is a full memory barrier in read_lock and
> read_unlock() vs sync_sched() in write.
>
> Full memory barriers are expensive and while the combined cost might
> well exceed the cost of the sync_sched() it
On Monday, July 11, 2016 10:29:44 AM CEST Patrice Chotard wrote:
> warning: refname 'sti-defconfig-for-v4.8' is ambiguous.
> Highlights:
> ---
> - Enable DRM_STI for STMicroelectronics DRM Support
> - VIDEO_STI_BDISP for STMicroelectronics BDISP 2D
>
Pulled into next/defconfig, thanks!
On Monday, July 11, 2016 10:29:44 AM CEST Patrice Chotard wrote:
> warning: refname 'sti-defconfig-for-v4.8' is ambiguous.
> Highlights:
> ---
> - Enable DRM_STI for STMicroelectronics DRM Support
> - VIDEO_STI_BDISP for STMicroelectronics BDISP 2D
>
Pulled into next/defconfig, thanks!
Hi Ingo,
I agree with you but it can affect a lot of systems according to
163ea310b68bdde89b1ac633fbf8c0db290d3f86.
Do you think we should invert 163ea310 instead?
On Thu, Jul 14, 2016 at 8:58 PM, Ingo Molnar wrote:
>
> * Alex Hung wrote:
>
>> Dell
Hi Ingo,
I agree with you but it can affect a lot of systems according to
163ea310b68bdde89b1ac633fbf8c0db290d3f86.
Do you think we should invert 163ea310 instead?
On Thu, Jul 14, 2016 at 8:58 PM, Ingo Molnar wrote:
>
> * Alex Hung wrote:
>
>> Dell Optiplex 7450 AIO works with BOOT_ACPI;
On Thu, 2016-07-14 at 12:10:46 +0200, Christophe JAILLET wrote:
> In function 'xilinx_pcie_init_irq_domain', the pattern used to check and
> return error is:
>
>if (!var) {
> dev_err(...);
> return PTR_ERR(var);
>}
>
> So the returned value in case of error is always 0, which
On 7 July 2016 at 18:59, Ard Biesheuvel wrote:
> The 100c08 scratch page is mapped using dma_map_page() before the TTM
> layer has had a chance to set the DMA mask. This means we are still
> running with the default of 32 when this code executes, and this causes
>
1001 - 1100 of 1844 matches
Mail list logo