On Wed, Sep 12, 2018 at 9:22 AM zhong jiang wrote:
>
> platform_driver_register will set the .owner field. So it is safe
> to remove the redundant assignment.
>
> The issue is detected with the help of Coccinelle.
>
> Signed-off-by: zhong jiang
> ---
> drivers/staging/greybus/audio_codec.c|
On Wed, Sep 12, 2018 at 9:22 AM zhong jiang wrote:
>
> platform_driver_register will set the .owner field. So it is safe
> to remove the redundant assignment.
>
> The issue is detected with the help of Coccinelle.
>
> Signed-off-by: zhong jiang
> ---
> drivers/staging/greybus/audio_codec.c|
Hi Reinette,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.19-rc3 next-20180911]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Reinette,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.19-rc3 next-20180911]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Wed, Sep 12, 2018 at 01:25:27PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 02a5c550b2738f2bfea8e1e00aa75944d71c9e18 ("rcu: Abstract extended
> quiescent state determination")
>
On Wed, Sep 12, 2018 at 01:25:27PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 02a5c550b2738f2bfea8e1e00aa75944d71c9e18 ("rcu: Abstract extended
> quiescent state determination")
>
On Wed, Sep 12, 2018 at 02:50:08AM +, YueHaibing wrote:
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Signed-off-by: YueHaibing
> ---
> drivers/staging/mt7621-pci/pci-mt7621.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git
On Wed, Sep 12, 2018 at 02:50:08AM +, YueHaibing wrote:
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Signed-off-by: YueHaibing
> ---
> drivers/staging/mt7621-pci/pci-mt7621.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git
On Tue, 11 Sep 2018 22:26:54 +0200
Arnd Bergmann wrote:
> On Sun, Sep 9, 2018 at 6:12 AM Al Viro wrote:
> >
> > On Sat, Sep 08, 2018 at 04:28:12PM +0200, Arnd Bergmann wrote:
> > > These are all handled by the random driver, so instead of listing
> > > each ioctl, we can just use the same
On Tue, 11 Sep 2018 22:26:54 +0200
Arnd Bergmann wrote:
> On Sun, Sep 9, 2018 at 6:12 AM Al Viro wrote:
> >
> > On Sat, Sep 08, 2018 at 04:28:12PM +0200, Arnd Bergmann wrote:
> > > These are all handled by the random driver, so instead of listing
> > > each ioctl, we can just use the same
2018-09-12 13:35 GMT+09:00 Vinod :
> On 12-09-18, 12:01, Masahiro Yamada wrote:
>> Hi Vinod,
>>
>>
>> 2018-09-11 16:00 GMT+09:00 Vinod :
>> > On 24-08-18, 10:41, Masahiro Yamada wrote:
>> >
>> >> +/* mc->vc.lock must be held by caller */
>> >> +static u32 __uniphier_mdmac_get_residue(struct
2018-09-12 13:35 GMT+09:00 Vinod :
> On 12-09-18, 12:01, Masahiro Yamada wrote:
>> Hi Vinod,
>>
>>
>> 2018-09-11 16:00 GMT+09:00 Vinod :
>> > On 24-08-18, 10:41, Masahiro Yamada wrote:
>> >
>> >> +/* mc->vc.lock must be held by caller */
>> >> +static u32 __uniphier_mdmac_get_residue(struct
FYI, we noticed the following commit (built with gcc-7):
commit: 02a5c550b2738f2bfea8e1e00aa75944d71c9e18 ("rcu: Abstract extended
quiescent state determination")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: perf_event_tests
with following parameters:
FYI, we noticed the following commit (built with gcc-7):
commit: 02a5c550b2738f2bfea8e1e00aa75944d71c9e18 ("rcu: Abstract extended
quiescent state determination")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: perf_event_tests
with following parameters:
On Tue, Sep 11, 2018 at 09:58:48PM -0700, Guenter Roeck wrote:
> On 09/11/2018 09:58 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Trivial fix to spelling mistake in comment
> >
> > Signed-off-by: Colin Ian King
>
> Reviewed-by: Guenter Roeck
>
> Interesting -
On Tue, Sep 11, 2018 at 09:58:48PM -0700, Guenter Roeck wrote:
> On 09/11/2018 09:58 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Trivial fix to spelling mistake in comment
> >
> > Signed-off-by: Colin Ian King
>
> Reviewed-by: Guenter Roeck
>
> Interesting -
Hi everyone,
Helios4, an Armada 388 based NAS SBC, provides 2 (4-pins) fan connectors.
The PWM pins on both connector are connected to GPIO on bank 1. Current
gpio-mvebu does not allow more than one PWM on the same bank.
Aditya
---
Changes v1->v2:
* Merge/squash "[Patch 2/2] gpio: mvebu:
Allow more than 1 PWM request (eg. PWM fan) on the same GPIO chip. If
the other PWM counter is unused, allocate it to next PWM request.
The priority would be:
1. Default counter assigned to the bank
2. Unused counter that is assigned to other bank
Since there are only two PWM counters, only two
Hi everyone,
Helios4, an Armada 388 based NAS SBC, provides 2 (4-pins) fan connectors.
The PWM pins on both connector are connected to GPIO on bank 1. Current
gpio-mvebu does not allow more than one PWM on the same bank.
Aditya
---
Changes v1->v2:
* Merge/squash "[Patch 2/2] gpio: mvebu:
Allow more than 1 PWM request (eg. PWM fan) on the same GPIO chip. If
the other PWM counter is unused, allocate it to next PWM request.
The priority would be:
1. Default counter assigned to the bank
2. Unused counter that is assigned to other bank
Since there are only two PWM counters, only two
On Tue, Sep 11, 2018 at 9:25 PM, Masahiro Yamada
wrote:
> You can always prefix variant/platform header search paths with
> $(srctree)/ because $(srctree) is '.' for in-tree building.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> arch/xtensa/Makefile | 4
> 1 file changed, 4 deletions(-)
On Tue, Sep 11, 2018 at 9:25 PM, Masahiro Yamada
wrote:
> You can always prefix variant/platform header search paths with
> $(srctree)/ because $(srctree) is '.' for in-tree building.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> arch/xtensa/Makefile | 4
> 1 file changed, 4 deletions(-)
On 09/07/2018 10:19 AM, Matthew Wilcox wrote:
On Fri, Sep 07, 2018 at 09:05:39AM +0800, kernel test robot wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit
On 09/07/2018 10:19 AM, Matthew Wilcox wrote:
On Fri, Sep 07, 2018 at 09:05:39AM +0800, kernel test robot wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit
On 09/11/2018 09:58 AM, Colin King wrote:
From: Colin Ian King
Trivial fix to spelling mistake in comment
Signed-off-by: Colin Ian King
Reviewed-by: Guenter Roeck
Interesting - drivers/firmware/google/ does not have a maintainer.
Greg - is it correct to assume that you are the de-facto
On 09/11/2018 09:58 AM, Colin King wrote:
From: Colin Ian King
Trivial fix to spelling mistake in comment
Signed-off-by: Colin Ian King
Reviewed-by: Guenter Roeck
Interesting - drivers/firmware/google/ does not have a maintainer.
Greg - is it correct to assume that you are the de-facto
$(srctree) always points to the top of the source tree whether
KBUILD_SRC is set or not.
Signed-off-by: Masahiro Yamada
---
scripts/Kbuild.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index ce53639..46cc43e 100644
$(srctree) always points to the top of the source tree whether
KBUILD_SRC is set or not.
Signed-off-by: Masahiro Yamada
---
scripts/Kbuild.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index ce53639..46cc43e 100644
Hi all,
News: there will be no linux-next releases on Friday or Monday.
Changes since 20180911:
Dropped trees: xarray, ida (temporarily)
I applied a patch for a runtime problem in the vfs tree and I still
disabled building some samples.
The drm-misc tree gained a conflict against the drm tree
Hi all,
News: there will be no linux-next releases on Friday or Monday.
Changes since 20180911:
Dropped trees: xarray, ida (temporarily)
I applied a patch for a runtime problem in the vfs tree and I still
disabled building some samples.
The drm-misc tree gained a conflict against the drm tree
On 12-09-18, 12:01, Masahiro Yamada wrote:
> Hi Vinod,
>
>
> 2018-09-11 16:00 GMT+09:00 Vinod :
> > On 24-08-18, 10:41, Masahiro Yamada wrote:
> >
> >> +/* mc->vc.lock must be held by caller */
> >> +static u32 __uniphier_mdmac_get_residue(struct uniphier_mdmac_desc *md)
> >> +{
> >> + u32
On 12-09-18, 12:01, Masahiro Yamada wrote:
> Hi Vinod,
>
>
> 2018-09-11 16:00 GMT+09:00 Vinod :
> > On 24-08-18, 10:41, Masahiro Yamada wrote:
> >
> >> +/* mc->vc.lock must be held by caller */
> >> +static u32 __uniphier_mdmac_get_residue(struct uniphier_mdmac_desc *md)
> >> +{
> >> + u32
On Mon, Sep 10, 2018 at 7:16 PM, Christoph Hellwig wrote:
> On Fri, Sep 07, 2018 at 06:14:29PM +0530, Anup Patel wrote:
>> This patch provides arch_show_interrupts() implementation to
>> show IPI stats via /proc/interrupts.
>>
>> Now the contents of /proc/interrupts" will look like below:
>>
On Mon, Sep 10, 2018 at 7:16 PM, Christoph Hellwig wrote:
> On Fri, Sep 07, 2018 at 06:14:29PM +0530, Anup Patel wrote:
>> This patch provides arch_show_interrupts() implementation to
>> show IPI stats via /proc/interrupts.
>>
>> Now the contents of /proc/interrupts" will look like below:
>>
You can always prefix variant/platform header search paths with
$(srctree)/ because $(srctree) is '.' for in-tree building.
Signed-off-by: Masahiro Yamada
---
arch/xtensa/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/arch/xtensa/Makefile b/arch/xtensa/Makefile
index
You can always prefix variant/platform header search paths with
$(srctree)/ because $(srctree) is '.' for in-tree building.
Signed-off-by: Masahiro Yamada
---
arch/xtensa/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/arch/xtensa/Makefile b/arch/xtensa/Makefile
index
You can always prefix machine/plat header search paths with
$(srctree)/ because $(srctree) is '.' for in-tree building.
Signed-off-by: Masahiro Yamada
---
KernelVersion: v4.19-rc3
arch/arm/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/Makefile b/arch/arm/Makefile
You can always prefix machine/plat header search paths with
$(srctree)/ because $(srctree) is '.' for in-tree building.
Signed-off-by: Masahiro Yamada
---
KernelVersion: v4.19-rc3
arch/arm/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/Makefile b/arch/arm/Makefile
Hi Arnd, Nick, Stefan,
On Mon, Sep 10, 2018 at 2:14 PM, Arnd Bergmann wrote:
> On Mon, Sep 10, 2018 at 8:05 AM Stefan Agner wrote:
>>
>> ARM32 arch code uses the __naked attribute. This has previously been
>> defined in include/linux/compiler-gcc.h, which is no longer included
>> for Clang.
Hi Arnd, Nick, Stefan,
On Mon, Sep 10, 2018 at 2:14 PM, Arnd Bergmann wrote:
> On Mon, Sep 10, 2018 at 8:05 AM Stefan Agner wrote:
>>
>> ARM32 arch code uses the __naked attribute. This has previously been
>> defined in include/linux/compiler-gcc.h, which is no longer included
>> for Clang.
Introuduce linux generic suspend states supported properties.
It is convenient for the generic suspend path to have
the knowledge of the suspend states supported based on the
device tree properties based on which it can either be suspended
or safely bailed out of suspend if none of the suspend
Introuduce linux generic suspend states supported properties.
It is convenient for the generic suspend path to have
the knowledge of the suspend states supported based on the
device tree properties based on which it can either be suspended
or safely bailed out of suspend if none of the suspend
On 11-09-18, 14:58, Yu Zhao wrote:
> On Tue, Sep 11, 2018 at 08:06:49AM +0200, Takashi Iwai wrote:
> > On Mon, 10 Sep 2018 23:21:50 +0200,
> > Yu Zhao wrote:
> > >
> > > In snd_hdac_bus_init_chip(), we enable interrupt before
> > > snd_hdac_bus_init_cmd_io() initializing dma buffers. If irq has
>
On 11-09-18, 14:58, Yu Zhao wrote:
> On Tue, Sep 11, 2018 at 08:06:49AM +0200, Takashi Iwai wrote:
> > On Mon, 10 Sep 2018 23:21:50 +0200,
> > Yu Zhao wrote:
> > >
> > > In snd_hdac_bus_init_chip(), we enable interrupt before
> > > snd_hdac_bus_init_cmd_io() initializing dma buffers. If irq has
>
On Wed, 12 Sep 2018 10:08:37 +0800
"Leizhen (ThunderTown)" wrote:
> After patch 7e066fb870fc ("tracepoints: add DECLARE_TRACE() and
> DEFINE_TRACE()"),
> the trace APIs declared by "TRACE_EVENT(irq_handler_entry" can not be
> directly used
> by ko, because it's not explicitly exported by
On Wed, 12 Sep 2018 10:08:37 +0800
"Leizhen (ThunderTown)" wrote:
> After patch 7e066fb870fc ("tracepoints: add DECLARE_TRACE() and
> DEFINE_TRACE()"),
> the trace APIs declared by "TRACE_EVENT(irq_handler_entry" can not be
> directly used
> by ko, because it's not explicitly exported by
platform_driver_register will set the .owner field. So it is safe
to remove the redundant assignment.
The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
sound/soc/mediatek/mt2701/mt2701-wm8960.c | 1 -
sound/soc/mediatek/mt6797/mt6797-mt6351.c | 1 -
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
MAINTAINERS | 2 +-
Makefile| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W:
platform_driver_register will set the .owner field. So it is safe
to remove the redundant assignment.
The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
sound/soc/mediatek/mt2701/mt2701-wm8960.c | 1 -
sound/soc/mediatek/mt6797/mt6797-mt6351.c | 1 -
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
MAINTAINERS | 2 +-
Makefile| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W:
platform_driver_register will set the .owner field. So it is safe
to remove the redundant assignment.
The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
drivers/staging/greybus/audio_codec.c| 1 -
drivers/staging/mt7621-eth/gsw_mt7621.c | 1 -
platform_driver_register will set the .owner field. So it is safe
to remove the redundant assignment.
The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
drivers/staging/greybus/audio_codec.c| 1 -
drivers/staging/mt7621-eth/gsw_mt7621.c | 1 -
arch/sparc/vdso/Makefile is a replica of arch/x86/entry/vdso/Makefile.
Clean-up the Makefile in the same way as I did for x86:
- Remove unnecessary export
- Put the generated linker script to $(obj)/ instead of $(src)/
- Simplify cmd_vdso2c
The corresponding x86 commits are:
- 61615faf0a89
arch/sparc/vdso/Makefile is a replica of arch/x86/entry/vdso/Makefile.
Clean-up the Makefile in the same way as I did for x86:
- Remove unnecessary export
- Put the generated linker script to $(obj)/ instead of $(src)/
- Simplify cmd_vdso2c
The corresponding x86 commits are:
- 61615faf0a89
persistent_ram_vmap() returns the page start vaddr.
persistent_ram_iomap() supports non-page-aligned mapping.
persistent_ram_buffer_map() always adds offset-in-page to the vaddr
returned from these two functions, which causes incorrect mapping of
non-page-aligned persistent ram buffer.
persistent_ram_vmap() returns the page start vaddr.
persistent_ram_iomap() supports non-page-aligned mapping.
persistent_ram_buffer_map() always adds offset-in-page to the vaddr
returned from these two functions, which causes incorrect mapping of
non-page-aligned persistent ram buffer.
On Fri, 2018-09-07 at 13:09 -0500, Rob Herring wrote:
> On Thu, Sep 6, 2018 at 9:21 PM Ley Foon Tan
> wrote:
> >
> >
> > On Wed, 2018-09-05 at 18:53 -0500, Rob Herring wrote:
> > >
> > > Align nios2 with other architectures which build the dtb files in
> > > the
> > > same directory as the dts
On Fri, 2018-09-07 at 13:09 -0500, Rob Herring wrote:
> On Thu, Sep 6, 2018 at 9:21 PM Ley Foon Tan
> wrote:
> >
> >
> > On Wed, 2018-09-05 at 18:53 -0500, Rob Herring wrote:
> > >
> > > Align nios2 with other architectures which build the dtb files in
> > > the
> > > same directory as the dts
On 09/11/18 at 08:08pm, Baoquan He wrote:
> On 09/11/18 at 11:28am, Ingo Molnar wrote:
> > Yeah, so proper context is still missing, this paragraph appears to assume
> > from the reader a
> > whole lot of prior knowledge, and this is one of the top comments in
> > kaslr.c so there's nowhere
>
On 09/11/18 at 08:08pm, Baoquan He wrote:
> On 09/11/18 at 11:28am, Ingo Molnar wrote:
> > Yeah, so proper context is still missing, this paragraph appears to assume
> > from the reader a
> > whole lot of prior knowledge, and this is one of the top comments in
> > kaslr.c so there's nowhere
>
> While testing, I got curious, as a 'perf test' user, why one of the
> tests had the "Skip" result:
>
> [root@seventh ~]# perf test watchpoint
> 22: Watchpoint:
> 22.1: Read Only Watchpoint: Skip
> 22.2: Write Only
> While testing, I got curious, as a 'perf test' user, why one of the
> tests had the "Skip" result:
>
> [root@seventh ~]# perf test watchpoint
> 22: Watchpoint:
> 22.1: Read Only Watchpoint: Skip
> 22.2: Write Only
Hi Ezequiel,
On Tue, Sep 11, 2018 at 04:40:29PM -0300, Ezequiel Garcia wrote:
> On Tue, 2018-09-11 at 08:00 +0530, Manivannan Sadhasivam wrote:
> > Since the same family members of Rock960 boards (Rock960 and Ficus)
> > share the same configuration, split out the common nodes into a common
> >
Hi Ezequiel,
On Tue, Sep 11, 2018 at 04:40:29PM -0300, Ezequiel Garcia wrote:
> On Tue, 2018-09-11 at 08:00 +0530, Manivannan Sadhasivam wrote:
> > Since the same family members of Rock960 boards (Rock960 and Ficus)
> > share the same configuration, split out the common nodes into a common
> >
On 09/10/2018 11:01 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 10, 2018 at 11:18:30AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Sep 10, 2018 at 10:47:54AM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
On Mon,
On 09/10/2018 11:01 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 10, 2018 at 11:18:30AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Sep 10, 2018 at 10:47:54AM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
On Mon,
Hi Vinod,
2018-09-11 16:00 GMT+09:00 Vinod :
> On 24-08-18, 10:41, Masahiro Yamada wrote:
>
>> +/* mc->vc.lock must be held by caller */
>> +static u32 __uniphier_mdmac_get_residue(struct uniphier_mdmac_desc *md)
>> +{
>> + u32 residue = 0;
>> + int i;
>> +
>> + for (i = md->sg_cur;
Hi Vinod,
2018-09-11 16:00 GMT+09:00 Vinod :
> On 24-08-18, 10:41, Masahiro Yamada wrote:
>
>> +/* mc->vc.lock must be held by caller */
>> +static u32 __uniphier_mdmac_get_residue(struct uniphier_mdmac_desc *md)
>> +{
>> + u32 residue = 0;
>> + int i;
>> +
>> + for (i = md->sg_cur;
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Signed-off-by: YueHaibing
---
drivers/staging/mt7621-pci/pci-mt7621.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
index
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Signed-off-by: YueHaibing
---
drivers/staging/mt7621-pci/pci-mt7621.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
index
This patch removes a set but unused variable in quirks.c.
Fixes warning:
variable ‘mmio_sys_info’ set but not used [-Wunused-but-set-variable]
Signed-off-by: Joshua Abraham
---
drivers/pci/quirks.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
This patch removes a set but unused variable in quirks.c.
Fixes warning:
variable ‘mmio_sys_info’ set but not used [-Wunused-but-set-variable]
Signed-off-by: Joshua Abraham
---
drivers/pci/quirks.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
On Mon, Sep 10, 2018 at 1:55 PM Al Viro wrote:
>
> Hadn't that sucker been dead code since 0.98.2? What am I missing here?
> Note that this thing had quite a few functionality changes over those
> years; had they even been tested?
Looks about right to me. The only point that actually acts on
On Mon, Sep 10, 2018 at 1:55 PM Al Viro wrote:
>
> Hadn't that sucker been dead code since 0.98.2? What am I missing here?
> Note that this thing had quite a few functionality changes over those
> years; had they even been tested?
Looks about right to me. The only point that actually acts on
On Tue, Sep 11, 2018 at 04:35:03PM -0700, Yang Shi wrote:
> On 9/11/18 2:16 PM, Matthew Wilcox wrote:
> > On Wed, Sep 12, 2018 at 04:58:11AM +0800, Yang Shi wrote:
> > > mm/mmap.c | 97
> > > +--
> > I really think you're going about
On Tue, Sep 11, 2018 at 04:35:03PM -0700, Yang Shi wrote:
> On 9/11/18 2:16 PM, Matthew Wilcox wrote:
> > On Wed, Sep 12, 2018 at 04:58:11AM +0800, Yang Shi wrote:
> > > mm/mmap.c | 97
> > > +--
> > I really think you're going about
On Tue, Sep 11, 2018 at 11:17:07AM +0100, Suzuki K Poulose wrote:
> Switch to the updated coresight bindings.
>
> Cc: Shawn Guo
> Cc: Sascha Hauer
> Cc: Pengutronix Kernel Team
> Cc: Fabio Estevam
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
As per the convention we use for
On Tue, Sep 11, 2018 at 11:17:07AM +0100, Suzuki K Poulose wrote:
> Switch to the updated coresight bindings.
>
> Cc: Shawn Guo
> Cc: Sascha Hauer
> Cc: Pengutronix Kernel Team
> Cc: Fabio Estevam
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
As per the convention we use for
On Tue, Sep 11 2018 at 17:02 -0600, Matthias Kaehlcke wrote:
Hi Raju/Lina,
On Fri, Jul 27, 2018 at 03:34:46PM +0530, Raju P L S S S N wrote:
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such
On Tue, Sep 11 2018 at 17:02 -0600, Matthias Kaehlcke wrote:
Hi Raju/Lina,
On Fri, Jul 27, 2018 at 03:34:46PM +0530, Raju P L S S S N wrote:
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such
This driver was originally written by ST in 2016 as a misc input device
driver, and hasn't been maintained for a long time. I grabbed some code
from it's API and reformed it into a iio proximity device driver.
This version of driver uses i2c bus to talk to the sensor and
polling for measuring
This driver was originally written by ST in 2016 as a misc input device
driver, and hasn't been maintained for a long time. I grabbed some code
from it's API and reformed it into a iio proximity device driver.
This version of driver uses i2c bus to talk to the sensor and
polling for measuring
On Tue, Sep 11 2018 at 16:39 -0600, Matthias Kaehlcke wrote:
Hi Raju/Lina,
On Fri, Jul 27, 2018 at 03:34:44PM +0530, Raju P L S S S N wrote:
From: Lina Iyer
Allow the controller status be queried. The controller is busy if it is
actively processing request.
Signed-off-by: Lina Iyer
On Tue, Sep 11 2018 at 16:39 -0600, Matthias Kaehlcke wrote:
Hi Raju/Lina,
On Fri, Jul 27, 2018 at 03:34:44PM +0530, Raju P L S S S N wrote:
From: Lina Iyer
Allow the controller status be queried. The controller is busy if it is
actively processing request.
Signed-off-by: Lina Iyer
After patch 7e066fb870fc ("tracepoints: add DECLARE_TRACE() and
DEFINE_TRACE()"),
the trace APIs declared by "TRACE_EVENT(irq_handler_entry" can not be directly
used
by ko, because it's not explicitly exported by EXPORT_TRACEPOINT_SYMBOL_GPL or
EXPORT_TRACEPOINT_SYMBOL.
Did we miss it? or it's
After patch 7e066fb870fc ("tracepoints: add DECLARE_TRACE() and
DEFINE_TRACE()"),
the trace APIs declared by "TRACE_EVENT(irq_handler_entry" can not be directly
used
by ko, because it's not explicitly exported by EXPORT_TRACEPOINT_SYMBOL_GPL or
EXPORT_TRACEPOINT_SYMBOL.
Did we miss it? or it's
Thank you, Andi!
Yes, that's a situation, also it's an important one I guess.
Another case is that a process running inside a container has exited but
the container still alive.I think this is also a common case. The
potential fix solutions I am thinking are following:
- Using nsfs "device"
Thank you, Andi!
Yes, that's a situation, also it's an important one I guess.
Another case is that a process running inside a container has exited but
the container still alive.I think this is also a common case. The
potential fix solutions I am thinking are following:
- Using nsfs "device"
On Tue, Sep 11, 2018 at 04:58:44PM -0700, Jae Hyun Yoo wrote:
> On 9/11/2018 4:33 PM, Guenter Roeck wrote:
> >Looking into the patch, clearing the interrupt status at the end of an
> >interrupt handler is always suspicious and tends to result in race
> >conditions (because additional interrupts
On Tue, Sep 11, 2018 at 04:58:44PM -0700, Jae Hyun Yoo wrote:
> On 9/11/2018 4:33 PM, Guenter Roeck wrote:
> >Looking into the patch, clearing the interrupt status at the end of an
> >interrupt handler is always suspicious and tends to result in race
> >conditions (because additional interrupts
On Mon, Sep 10, 2018 at 11:37:52AM +0200, Alex Gonzalez wrote:
> The ConnectCore 6UL Single Board Computer (SBC) Pro contains the
> ConnectCore 6UL System-On-Module.
>
> Its hardware specifications are:
>
> * 256MB DDR3 memory
> * On module 256MB NAND flash
> * Dual 10/100 Ethernet
> * USB Host
On Mon, Sep 10, 2018 at 11:37:52AM +0200, Alex Gonzalez wrote:
> The ConnectCore 6UL Single Board Computer (SBC) Pro contains the
> ConnectCore 6UL System-On-Module.
>
> Its hardware specifications are:
>
> * 256MB DDR3 memory
> * On module 256MB NAND flash
> * Dual 10/100 Ethernet
> * USB Host
On Thu, Aug 02, 2018 at 12:34:25PM +0200, Oleksij Rempel wrote:
> This board, as well as some other boards with i.MX6 and a PMIC, uses a
> "PMIC_STBY_REQ" line to notify the PMIC about a state change.
> The PMIC is programmed for a specific state change before triggering the
> line.
> In this
On Thu, Aug 02, 2018 at 12:34:25PM +0200, Oleksij Rempel wrote:
> This board, as well as some other boards with i.MX6 and a PMIC, uses a
> "PMIC_STBY_REQ" line to notify the PMIC about a state change.
> The PMIC is programmed for a specific state change before triggering the
> line.
> In this
syzbot has found a reproducer for the following crash on:
HEAD commit:11da3a7f84f1 Linux 4.19-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11766c6940
kernel config: https://syzkaller.appspot.com/x/.config?x=9917ff4b798e1a1e
dashboard link:
syzbot has found a reproducer for the following crash on:
HEAD commit:11da3a7f84f1 Linux 4.19-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11766c6940
kernel config: https://syzkaller.appspot.com/x/.config?x=9917ff4b798e1a1e
dashboard link:
On Thu, Aug 02, 2018 at 12:34:21PM +0200, Oleksij Rempel wrote:
> One of the Freescale recommended sequences for power off with external
> PMIC is the following:
> ...
> 3. SoC is programming PMIC for power off when standby is asserted.
> 4. In CCM STOP mode, Standby is asserted, PMIC gates SoC
On Thu, Aug 02, 2018 at 12:34:21PM +0200, Oleksij Rempel wrote:
> One of the Freescale recommended sequences for power off with external
> PMIC is the following:
> ...
> 3. SoC is programming PMIC for power off when standby is asserted.
> 4. In CCM STOP mode, Standby is asserted, PMIC gates SoC
Hi!
[ Thanks a lot for upstreaming this.. ]
On Tue, Sep 11, 2018 at 02:34:57PM -0700, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add ZynqMP PM driver. PM driver provides power management
> support for ZynqMP.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
[...]
> +static
Hi!
[ Thanks a lot for upstreaming this.. ]
On Tue, Sep 11, 2018 at 02:34:57PM -0700, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add ZynqMP PM driver. PM driver provides power management
> support for ZynqMP.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
[...]
> +static
1 - 100 of 1292 matches
Mail list logo
