In P9, OCC allows for clearing the sensor min-max history. This patch
exports attribute to reset history when set will clear the history of
all the sensors owned by CSM and belonging to the chip.
Signed-off-by: Shilpasri G Bhat
---
This patch is on top of this
In P9, OCC allows for clearing the sensor min-max history. This patch
exports attribute to reset history when set will clear the history of
all the sensors owned by CSM and belonging to the chip.
Signed-off-by: Shilpasri G Bhat
---
This patch is on top of this patchset:
On Tue, Jul 25, 2017 at 8:05 PM, Arnd Bergmann wrote:
> We cannot reference priv->fbdev outside of the #ifdef:
>
> drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
> used [-Werror=unused-function]
> static int virtnet_restore_up(struct virtio_device
On Tue, Jul 25, 2017 at 8:05 PM, Arnd Bergmann wrote:
> We cannot reference priv->fbdev outside of the #ifdef:
>
> drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
> used [-Werror=unused-function]
> static int virtnet_restore_up(struct virtio_device *vdev)
>
On Wed 26-07-17 09:54:26, Anshuman Khandual wrote:
> On 07/25/2017 07:06 PM, Michal Hocko wrote:
> > On Tue 25-07-17 12:06:57, Anshuman Khandual wrote:
> > [...]
> >> diff --git a/tools/testing/selftests/vm/mremap_mirror_private_anon.c
> >>
On Wed 26-07-17 09:54:26, Anshuman Khandual wrote:
> On 07/25/2017 07:06 PM, Michal Hocko wrote:
> > On Tue 25-07-17 12:06:57, Anshuman Khandual wrote:
> > [...]
> >> diff --git a/tools/testing/selftests/vm/mremap_mirror_private_anon.c
> >>
On Tue 25-07-17 21:19:52, Andrea Arcangeli wrote:
> On Tue, Jul 25, 2017 at 06:04:00PM +0200, Michal Hocko wrote:
> > - down_write(>mmap_sem);
> > + if (tsk_is_oom_victim(current))
> > + down_write(>mmap_sem);
> > free_pgtables(, vma, FIRST_USER_ADDRESS, USER_PGTABLES_CEILING);
>
On Tue 25-07-17 21:19:52, Andrea Arcangeli wrote:
> On Tue, Jul 25, 2017 at 06:04:00PM +0200, Michal Hocko wrote:
> > - down_write(>mmap_sem);
> > + if (tsk_is_oom_victim(current))
> > + down_write(>mmap_sem);
> > free_pgtables(, vma, FIRST_USER_ADDRESS, USER_PGTABLES_CEILING);
>
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
Chnage in v2 :
Error handling for things done in s3c_i2sv2_probe().
sound/soc/samsung/s3c2412-i2s.c | 12 ++--
1 file changed, 10
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
Chnage in v2 :
Error handling for things done in s3c_i2sv2_probe().
sound/soc/samsung/s3c2412-i2s.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff
On Tue 25-07-17 20:26:19, Andrea Arcangeli wrote:
> On Tue, Jul 25, 2017 at 05:45:14PM +0200, Michal Hocko wrote:
> > That problem is real though as reported by David.
>
> I'm not against fixing it, I just think it's not a major concern, and
> the solution doesn't seem optimal as measured by
On Tue 25-07-17 20:26:19, Andrea Arcangeli wrote:
> On Tue, Jul 25, 2017 at 05:45:14PM +0200, Michal Hocko wrote:
> > That problem is real though as reported by David.
>
> I'm not against fixing it, I just think it's not a major concern, and
> the solution doesn't seem optimal as measured by
On Tuesday 25 July 2017 06:57 PM, Will Deacon wrote:
On Fri, Jul 07, 2017 at 05:33:57PM +0530, Pratyush Anand wrote:
Architecture like ARM64 currently allows to use default hw breakpoint
single step handler only to perf. However, some other users like few
systemtap tests or kernel test in
On Tuesday 25 July 2017 06:57 PM, Will Deacon wrote:
On Fri, Jul 07, 2017 at 05:33:57PM +0530, Pratyush Anand wrote:
Architecture like ARM64 currently allows to use default hw breakpoint
single step handler only to perf. However, some other users like few
systemtap tests or kernel test in
On Wed, 26 Jul 2017 07:00:33 +0200
Heiko Carstens wrote:
> On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote:
> > Hi Martin,
> >
> > my s390 qemu tests in linux-next stopped working a few days ago.
> > Bisect points to commit 's390/spinlock: add niai
On Wed, 26 Jul 2017 07:00:33 +0200
Heiko Carstens wrote:
> On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote:
> > Hi Martin,
> >
> > my s390 qemu tests in linux-next stopped working a few days ago.
> > Bisect points to commit 's390/spinlock: add niai spinlock hints'.
> >
> >
We should pre-ack async tx descriptor at time of
allocating SBA request (just like other RAID drivers).
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 1 +
1
We should pre-ack async tx descriptor at time of
allocating SBA request (just like other RAID drivers).
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dma/bcm-sba-raid.c
We should peek mbox channels when we are left with no free
sba_requests in sba_alloc_request()
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 25
This patch adds Broadcom SBA-RAID DT nodes for Stingray SoC.
The Stingray SoC has total 32 SBA-RAID FlexRM rings and it has
8 CPUs so we create 8 SBA-RAID instances (one for each CPU).
This way Linux DMAENGINE will have one SBA-RAID DMA device for
each CPU.
Signed-off-by: Anup Patel
This patch breaks sba_process_deferred_requests() into two parts
sba_process_received_request() and _sba_process_pending_requests()
for readability.
In addition, we remove redundant SBA_REQUEST_STATE_RECEIVED state
and ensure that all requests in a chained request should be freed
only after all
This patch adds debugfs support to report stats via debugfs
which in-turn will help debug hang situations.
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 82
We should peek mbox channels when we are left with no free
sba_requests in sba_alloc_request()
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git
This patch adds Broadcom SBA-RAID DT nodes for Stingray SoC.
The Stingray SoC has total 32 SBA-RAID FlexRM rings and it has
8 CPUs so we create 8 SBA-RAID instances (one for each CPU).
This way Linux DMAENGINE will have one SBA-RAID DMA device for
each CPU.
Signed-off-by: Anup Patel
---
This patch breaks sba_process_deferred_requests() into two parts
sba_process_received_request() and _sba_process_pending_requests()
for readability.
In addition, we remove redundant SBA_REQUEST_STATE_RECEIVED state
and ensure that all requests in a chained request should be freed
only after all
This patch adds debugfs support to report stats via debugfs
which in-turn will help debug hang situations.
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/dma/bcm-sba-raid.c | 82 +-
1 file changed, 81
This patchset does various improvments to Broadcom SBA-RAID
driver and also adds SBA-RAID DT nodes for Stingray SOC.
The patches are based on "[PATCH v2 0/7] FlexRM driver improvements"
and can also be found at sba-raid-imp-v1 branch of
https://github.com/Broadcom/arm64-linux.git
Anup Patel (6):
This patchset does various improvments to Broadcom SBA-RAID
driver and also adds SBA-RAID DT nodes for Stingray SOC.
The patches are based on "[PATCH v2 0/7] FlexRM driver improvements"
and can also be found at sba-raid-imp-v1 branch of
https://github.com/Broadcom/arm64-linux.git
Anup Patel (6):
This patch improves memory allocation in SBA RAID driver in
following ways:
1. Simplify struct sba_request to reduce memory consumption
2. Allocate sba resources before registering dma device
Signed-off-by: Anup Patel
Reviewed-by: Scott Branden
This patch improves memory allocation in SBA RAID driver in
following ways:
1. Simplify struct sba_request to reduce memory consumption
2. Allocate sba resources before registering dma device
Signed-off-by: Anup Patel
Reviewed-by: Scott Branden
Reviewed-by: Ray Jui
Reviewed-by: Vikram Prakash
Hi Will,
Thanks for your review.
On Tuesday 25 July 2017 06:55 PM, Will Deacon wrote:
On Fri, Jul 07, 2017 at 05:34:00PM +0530, Pratyush Anand wrote:
If an interrupt is generated between breakpoint and step handler then
step handler can not get correct step address. This situation can easily
Hi Will,
Thanks for your review.
On Tuesday 25 July 2017 06:55 PM, Will Deacon wrote:
On Fri, Jul 07, 2017 at 05:34:00PM +0530, Pratyush Anand wrote:
If an interrupt is generated between breakpoint and step handler then
step handler can not get correct step address. This situation can easily
On Mon, Jul 24, 2017 at 01:55:10PM +, Pierre Yves MORDRET wrote:
> >> +
> >> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> >> + if (!res)
> >> + return -ENODEV;
> >> +
> >> + iomem = devm_ioremap_resource(>dev, res);
> >> + if (!iomem)
> >> + return -ENOMEM;
On Mon, Jul 24, 2017 at 01:55:10PM +, Pierre Yves MORDRET wrote:
> >> +
> >> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> >> + if (!res)
> >> + return -ENODEV;
> >> +
> >> + iomem = devm_ioremap_resource(>dev, res);
> >> + if (!iomem)
> >> + return -ENOMEM;
On Tue, 25 Jul 2017 19:57:17 PDT (-0700), j.neuschae...@gmx.net wrote:
> On Tue, Jul 11, 2017 at 06:31:30PM -0700, Palmer Dabbelt wrote:
>> This patch contains all the build infastructure that actually enables
>> the RISC-V port. This includes Makefiles, linker scripts, and Kconfig
>> files. It
On Tue, 25 Jul 2017 19:57:17 PDT (-0700), j.neuschae...@gmx.net wrote:
> On Tue, Jul 11, 2017 at 06:31:30PM -0700, Palmer Dabbelt wrote:
>> This patch contains all the build infastructure that actually enables
>> the RISC-V port. This includes Makefiles, linker scripts, and Kconfig
>> files. It
Hi,
On 07/26/2017 01:11 PM, Xing, Zhengjun wrote:
>
>
> On 7/25/2017 1:09 PM, Lu Baolu wrote:
>> Xhci driver handles USB transaction errors on transfer events,
>> but transaction errors are possible on address device command
>> completion events as well.
>>
>> The xHCI specification (section
Hi,
On 07/26/2017 01:11 PM, Xing, Zhengjun wrote:
>
>
> On 7/25/2017 1:09 PM, Lu Baolu wrote:
>> Xhci driver handles USB transaction errors on transfer events,
>> but transaction errors are possible on address device command
>> completion events as well.
>>
>> The xHCI specification (section
This patch adds support to set power-shifting-ratio for CPU-GPU which
is used by OCC power capping algorithm.
Signed-off-by: Shilpasri G Bhat
---
Changes from V7:
- Replaced sscanf with kstrtoint
arch/powerpc/include/asm/opal-api.h| 4 +-
This patch adds support to set power-shifting-ratio for CPU-GPU which
is used by OCC power capping algorithm.
Signed-off-by: Shilpasri G Bhat
---
Changes from V7:
- Replaced sscanf with kstrtoint
arch/powerpc/include/asm/opal-api.h| 4 +-
arch/powerpc/include/asm/opal.h
Adds support for clearing different sensor groups. OCC inband sensor
groups like CSM, Profiler, Job Scheduler can be cleared using this
driver. The min/max of all sensors belonging to these sensor groups
will be cleared.
Signed-off-by: Shilpasri G Bhat
---
Changes
Adds a generic powercap framework to change the system powercap
inband through OPAL-OCC command/response interface.
Signed-off-by: Shilpasri G Bhat
---
Changes from V7:
- Replaced sscanf with kstrtoint
arch/powerpc/include/asm/opal-api.h| 5 +-
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. The following commands are supported:
1) Set system powercap
2) Set CPU-GPU
Adds support for clearing different sensor groups. OCC inband sensor
groups like CSM, Profiler, Job Scheduler can be cleared using this
driver. The min/max of all sensors belonging to these sensor groups
will be cleared.
Signed-off-by: Shilpasri G Bhat
---
Changes from V7:
-
Adds a generic powercap framework to change the system powercap
inband through OPAL-OCC command/response interface.
Signed-off-by: Shilpasri G Bhat
---
Changes from V7:
- Replaced sscanf with kstrtoint
arch/powerpc/include/asm/opal-api.h| 5 +-
arch/powerpc/include/asm/opal.h
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. The following commands are supported:
1) Set system powercap
2) Set CPU-GPU
On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote:
> Hi Martin,
>
> my s390 qemu tests in linux-next stopped working a few days ago.
> Bisect points to commit 's390/spinlock: add niai spinlock hints'.
>
> Looking at the patch, this isn't really surprising; at least to me it looks
>
On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote:
> Hi Martin,
>
> my s390 qemu tests in linux-next stopped working a few days ago.
> Bisect points to commit 's390/spinlock: add niai spinlock hints'.
>
> Looking at the patch, this isn't really surprising; at least to me it looks
>
On Mon, Jul 24, 2017 at 09:34:18AM +, Pierre Yves MORDRET wrote:
>
> On 07/21/2017 12:32 PM, Pierre Yves MORDRET wrote:
> >
> >
> > On 07/21/2017 11:54 AM, Vinod Koul wrote:
> >> On Fri, Jul 21, 2017 at 09:30:00AM +, Pierre Yves MORDRET wrote:
> > +static enum dma_slave_buswidth
On Mon, Jul 24, 2017 at 09:34:18AM +, Pierre Yves MORDRET wrote:
>
> On 07/21/2017 12:32 PM, Pierre Yves MORDRET wrote:
> >
> >
> > On 07/21/2017 11:54 AM, Vinod Koul wrote:
> >> On Fri, Jul 21, 2017 at 09:30:00AM +, Pierre Yves MORDRET wrote:
> > +static enum dma_slave_buswidth
adding SDI to drm connector list
Signed-off-by: Saurabh Sengar
---
drivers/gpu/drm/drm_connector.c | 1 +
include/uapi/drm/drm_mode.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
index
adding SDI to drm connector list
Signed-off-by: Saurabh Sengar
---
drivers/gpu/drm/drm_connector.c | 1 +
include/uapi/drm/drm_mode.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
index 2db7fb5..ea48ddb 100644
---
On Mon, Jun 26, 2017 at 05:49:30PM -0500, Tom Zanussi wrote:
> With the addition of variables and actions, it's become necessary to
> provide more detailed error information to users about syntax errors.
>
> Add a 'last error' facility accessible via the erroring event's 'hist'
> file. Reading
On Mon, Jun 26, 2017 at 05:49:30PM -0500, Tom Zanussi wrote:
> With the addition of variables and actions, it's become necessary to
> provide more detailed error information to users about syntax errors.
>
> Add a 'last error' facility accessible via the erroring event's 'hist'
> file. Reading
On Wed, Jul 26, 2017 at 06:24:39AM +0200, Richard Cochran wrote:
> Thanks for coding this up. I'd like to get some broader review. On
> the next round, please include lkml, John Stultz, and Thomas Gleixner.
I just noticed that you already have lkml.
Thanks,
Richard
On Wed, Jul 26, 2017 at 06:24:39AM +0200, Richard Cochran wrote:
> Thanks for coding this up. I'd like to get some broader review. On
> the next round, please include lkml, John Stultz, and Thomas Gleixner.
I just noticed that you already have lkml.
Thanks,
Richard
On Mon, Jul 24, 2017 at 02:07:43PM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> Provide support for Secure Encyrpted Virtualization (SEV). This initial
Your subject misses a verb and patch subjects should have an active verb
denoting what the patch does. The
On Mon, Jul 24, 2017 at 02:07:43PM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> Provide support for Secure Encyrpted Virtualization (SEV). This initial
Your subject misses a verb and patch subjects should have an active verb
denoting what the patch does. The sentence above is a good
On 07/25/2017 07:06 PM, Michal Hocko wrote:
> On Tue 25-07-17 12:06:57, Anshuman Khandual wrote:
> [...]
>> diff --git a/tools/testing/selftests/vm/mremap_mirror_private_anon.c
>> b/tools/testing/selftests/vm/mremap_mirror_private_anon.c
> [...]
>> +ptr = mmap(NULL, alloc_size, PROT_READ |
On 07/25/2017 07:06 PM, Michal Hocko wrote:
> On Tue 25-07-17 12:06:57, Anshuman Khandual wrote:
> [...]
>> diff --git a/tools/testing/selftests/vm/mremap_mirror_private_anon.c
>> b/tools/testing/selftests/vm/mremap_mirror_private_anon.c
> [...]
>> +ptr = mmap(NULL, alloc_size, PROT_READ |
Thanks for coding this up. I'd like to get some broader review. On
the next round, please include lkml, John Stultz, and Thomas Gleixner.
On Tue, Jul 25, 2017 at 03:24:18PM -0500, Grygorii Strashko wrote:
> @@ -217,6 +231,19 @@ struct ptp_clock *ptp_clock_register(struct
> ptp_clock_info
Thanks for coding this up. I'd like to get some broader review. On
the next round, please include lkml, John Stultz, and Thomas Gleixner.
On Tue, Jul 25, 2017 at 03:24:18PM -0500, Grygorii Strashko wrote:
> @@ -217,6 +231,19 @@ struct ptp_clock *ptp_clock_register(struct
> ptp_clock_info
From: Arnd Bergmann
Date: Tue, 25 Jul 2017 17:35:50 +0200
> After removing the reset function, the freeze and restore functions
> are now unused when CONFIG_PM_SLEEP is disabled:
>
> drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
> used
From: Arnd Bergmann
Date: Tue, 25 Jul 2017 17:35:50 +0200
> After removing the reset function, the freeze and restore functions
> are now unused when CONFIG_PM_SLEEP is disabled:
>
> drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
> used [-Werror=unused-function]
This SLUB free list pointer obfuscation code is modified from Brad
Spengler/PaX Team's code in the last public patch of grsecurity/PaX based
on my understanding of the code. Changes or omissions from the original
code are mine and don't reflect the original grsecurity/PaX code.
This adds a
This SLUB free list pointer obfuscation code is modified from Brad
Spengler/PaX Team's code in the last public patch of grsecurity/PaX based
on my understanding of the code. Changes or omissions from the original
code are mine and don't reflect the original grsecurity/PaX code.
This adds a
On Wed, Jul 26, 2017 at 7:54 AM, Icenowy Zheng wrote:
>
>
> 于 2017年7月25日 GMT+08:00 下午10:31:27, Maxime Ripard
> 写到:
>>On Tue, Jul 25, 2017 at 05:18:19AM +0200, Adam Borowski wrote:
>>> On Tue, Jul 25, 2017 at 11:04:24AM +0800, icen...@aosc.io
On Wed, Jul 26, 2017 at 7:54 AM, Icenowy Zheng wrote:
>
>
> 于 2017年7月25日 GMT+08:00 下午10:31:27, Maxime Ripard
> 写到:
>>On Tue, Jul 25, 2017 at 05:18:19AM +0200, Adam Borowski wrote:
>>> On Tue, Jul 25, 2017 at 11:04:24AM +0800, icen...@aosc.io wrote:
>>> > 在 2017-07-24 15:58,Maxime Ripard 写道:
>>>
Some irqchip drivers have a Kconfig prompt. When we run menuconfig
or friends, those drivers are directly listed in the "Device Drivers"
menu level. This does not look nice. Create a sub-system level menu.
Signed-off-by: Masahiro Yamada
---
Some irqchip drivers have a Kconfig prompt. When we run menuconfig
or friends, those drivers are directly listed in the "Device Drivers"
menu level. This does not look nice. Create a sub-system level menu.
Signed-off-by: Masahiro Yamada
---
drivers/irqchip/Kconfig | 4
1 file changed,
Currently KASLR will parse all e820 entries of RAM type and add all
candidate position into slots array. Then we will choose one slot
randomly as the new position which kernel will be decompressed into
and run at.
On system with EFI enabled, e820 memory regions are coming from EFI
memory regions
Currently KASLR will parse all e820 entries of RAM type and add all
candidate position into slots array. Then we will choose one slot
randomly as the new position which kernel will be decompressed into
and run at.
On system with EFI enabled, e820 memory regions are coming from EFI
memory regions
On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote:
> The examination of "current" to decide dumpability is wrong. This was a
> check of and euid/uid (or egid/gid) mismatch in the existing process,
> not the newly created one. This appears to stretch back into even the
>
On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote:
> The examination of "current" to decide dumpability is wrong. This was a
> check of and euid/uid (or egid/gid) mismatch in the existing process,
> not the newly created one. This appears to stretch back into even the
> "history.git" tree.
On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote:
> The Smack bprm_secureexec hook can be merged with the bprm_set_creds
> hook since it's dealing with the same information, and all of the details
> are finalized during the first call to the bprm_set_creds hook via
>
On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote:
> The Smack bprm_secureexec hook can be merged with the bprm_set_creds
> hook since it's dealing with the same information, and all of the details
> are finalized during the first call to the bprm_set_creds hook via
> prepare_binprm() (subsequent
On 2017年07月24日 21:38, Andrew Jones wrote:
Unregister the driver before removing multi-instance hotplug
callbacks. This order avoids the warning issued from
__cpuhp_remove_state_cpuslocked when the number of remaining
instances isn't yet zero.
Fixes: 8017c279196a ("net/virtio-net: Convert to
On Thu, Jul 20, 2017 at 04:52:08AM -0500, Suravee Suthikulpanit wrote:
> With X86_FEATURE_TOPOEXT, current logic default to using APIC ID
> to calculate cpumask for shared_cpu_map. However, since APIC IDs
> are not guarantee to be contiguous for cores across different L3,
> such as in family17h
On 2017年07月24日 21:38, Andrew Jones wrote:
Unregister the driver before removing multi-instance hotplug
callbacks. This order avoids the warning issued from
__cpuhp_remove_state_cpuslocked when the number of remaining
instances isn't yet zero.
Fixes: 8017c279196a ("net/virtio-net: Convert to
On Thu, Jul 20, 2017 at 04:52:08AM -0500, Suravee Suthikulpanit wrote:
> With X86_FEATURE_TOPOEXT, current logic default to using APIC ID
> to calculate cpumask for shared_cpu_map. However, since APIC IDs
> are not guarantee to be contiguous for cores across different L3,
> such as in family17h
While CONFIG_FORTIFY_SOURCE continues to shake out, don't unconditionally
use BUG(), opting instead for WARN(). At the same time, expand the runtime
detection to provide a better hint about what went wrong.
Cc: Daniel Micay
Suggested-by: Linus Torvalds
While CONFIG_FORTIFY_SOURCE continues to shake out, don't unconditionally
use BUG(), opting instead for WARN(). At the same time, expand the runtime
detection to provide a better hint about what went wrong.
Cc: Daniel Micay
Suggested-by: Linus Torvalds
Signed-off-by: Kees Cook
---
Sending to
On Tue, Jul 18, 2017 at 02:22:20PM -0300, Murilo Opsfelder Araujo wrote:
> When CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n, build fails with the
> following:
>
> drivers/vfio/pci/vfio_pci.o: In function `.vfio_pci_release':
> vfio_pci.c:(.text+0xa98): undefined reference to
>
On Tue, Jul 18, 2017 at 02:22:20PM -0300, Murilo Opsfelder Araujo wrote:
> When CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n, build fails with the
> following:
>
> drivers/vfio/pci/vfio_pci.o: In function `.vfio_pci_release':
> vfio_pci.c:(.text+0xa98): undefined reference to
>
On 07/23/2017 09:45 AM, Michael S. Tsirkin wrote:
On Fri, Jul 14, 2017 at 03:12:43PM +0800, Wei Wang wrote:
On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote:
On Thu, Jul 13, 2017 at 03:42:35PM +0800, Wei Wang wrote:
On 07/12/2017 09:56 PM, Michael S. Tsirkin wrote:
So the way I see it, there
On 07/23/2017 09:45 AM, Michael S. Tsirkin wrote:
On Fri, Jul 14, 2017 at 03:12:43PM +0800, Wei Wang wrote:
On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote:
On Thu, Jul 13, 2017 at 03:42:35PM +0800, Wei Wang wrote:
On 07/12/2017 09:56 PM, Michael S. Tsirkin wrote:
So the way I see it, there
This SoC is too old. It is difficult to maintain any longer.
Signed-off-by: Masahiro Yamada
---
.../devicetree/bindings/clock/uniphier-clock.txt | 5 ---
drivers/clk/uniphier/clk-uniphier-core.c | 16 +++--
This SoC is too old. It is difficult to maintain any longer.
Signed-off-by: Masahiro Yamada
---
.../devicetree/bindings/clock/uniphier-clock.txt | 5 ---
drivers/clk/uniphier/clk-uniphier-core.c | 16 +++--
drivers/clk/uniphier/clk-uniphier-mio.c| 4 +--
On 2017年07月25日 23:35, Arnd Bergmann wrote:
After removing the reset function, the freeze and restore functions
are now unused when CONFIG_PM_SLEEP is disabled:
drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
used [-Werror=unused-function]
static int
On 2017年07月25日 23:35, Arnd Bergmann wrote:
After removing the reset function, the freeze and restore functions
are now unused when CONFIG_PM_SLEEP is disabled:
drivers/net/virtio_net.c:1881:12: error: 'virtnet_restore_up' defined but not
used [-Werror=unused-function]
static int
On 2017年07月25日 05:29, Michael S. Tsirkin wrote:
On Wed, Jul 19, 2017 at 04:54:49PM +0800, Jason Wang wrote:
Current XDP implementation wants guest offloads feature to be disabled
on device. This is inconvenient and means guest can't benefit from
offloads if XDP is not used. This patch tries
On 2017年07月25日 05:29, Michael S. Tsirkin wrote:
On Wed, Jul 19, 2017 at 04:54:49PM +0800, Jason Wang wrote:
Current XDP implementation wants guest offloads feature to be disabled
on device. This is inconvenient and means guest can't benefit from
offloads if XDP is not used. This patch tries
On Tue, Jul 18, 2017 at 01:03:39PM +0200, Borislav Petkov wrote:
>On Sat, Jul 08, 2017 at 09:30:57AM +0800, Wei Yang wrote:
>> max_emu_nid and dfl_phys_nid is calculated from emu_nid_to_phys[], which is
>> calculated in split_nodes_xxx_interleave(). From the logic in these
>
>$ git grep
On Tue, Jul 18, 2017 at 01:03:39PM +0200, Borislav Petkov wrote:
>On Sat, Jul 08, 2017 at 09:30:57AM +0800, Wei Yang wrote:
>> max_emu_nid and dfl_phys_nid is calculated from emu_nid_to_phys[], which is
>> calculated in split_nodes_xxx_interleave(). From the logic in these
>
>$ git grep
Hi Manu,
On 25 July 2017 at 19:19, Manu Gautam wrote:
> Hi,
>
>
> On 7/25/2017 1:30 PM, Baolin Wang wrote:
>> This patch introduces the usb charger support based on usb phy that
>> makes an enhancement to a power driver. The basic conception of the
>> usb charger is that,
Hi Manu,
On 25 July 2017 at 19:19, Manu Gautam wrote:
> Hi,
>
>
> On 7/25/2017 1:30 PM, Baolin Wang wrote:
>> This patch introduces the usb charger support based on usb phy that
>> makes an enhancement to a power driver. The basic conception of the
>> usb charger is that, when one usb charger is
On 07/25/2017 12:15 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.63 release.
There are 60 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 07/25/2017 12:15 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.63 release.
There are 60 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Hi,
On 25 July 2017 at 17:59, Sebastian Reichel
wrote:
> Hi,
>
> On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote:
>> Integrate with the newly added USB charger interface to limit the current
>> we draw from the USB input based on the input device
Hi,
On 25 July 2017 at 17:59, Sebastian Reichel
wrote:
> Hi,
>
> On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote:
>> Integrate with the newly added USB charger interface to limit the current
>> we draw from the USB input based on the input device configuration
>> identified by the
1 - 100 of 2870 matches
Mail list logo