Hello,
whlie using this path i got another stall - which i never saw under
kernel 4.4. Here is the trace:
[305111.932698] INFO: task ksmtuned:1399 blocked for more than 120 seconds.
[305111.933612] Tainted: G 4.12.0+105-ph #1
[305111.934456] "echo 0 >
Hello,
whlie using this path i got another stall - which i never saw under
kernel 4.4. Here is the trace:
[305111.932698] INFO: task ksmtuned:1399 blocked for more than 120 seconds.
[305111.933612] Tainted: G 4.12.0+105-ph #1
[305111.934456] "echo 0 >
On Sun, 2 Sep 2018 15:29:23 +0200
Tomasz Duszynski wrote:
> Relying on CONFIG_PM_SLEEP to set PM ops is not necessary
> since core will handle everything internally. One have to only make sure
> that functions that can go unused are marked with __maybe_unused.
>
> Signed-off-by: Tomasz
On Sun, 2 Sep 2018 15:29:23 +0200
Tomasz Duszynski wrote:
> Relying on CONFIG_PM_SLEEP to set PM ops is not necessary
> since core will handle everything internally. One have to only make sure
> that functions that can go unused are marked with __maybe_unused.
>
> Signed-off-by: Tomasz
From: Dou Liyang
Linux has spread out the non managed interrupt across the possible
target CPUs to avoid vector space exhaustion.
But, the same situation may happen on the managed interrupts.
Spread managed interrupt on allocation as well.
Note: also change the return value for the empty
From: Dou Liyang
Linux finds the CPU which has the lowest vector allocation count to spread
out the non managed interrupt across the possible target CPUs.
This common CPU finding code will also be used in managed case,
So Split it out into a helper for preparation.
Signed-off-by: Dou Liyang
From: Dou Liyang
Linux has spread out the non managed interrupt across the possible
target CPUs to avoid vector space exhaustion.
But, the same situation may happen on the managed interrupts.
Spread managed interrupt on allocation as well.
Note: also change the return value for the empty
From: Dou Liyang
Linux finds the CPU which has the lowest vector allocation count to spread
out the non managed interrupt across the possible target CPUs.
This common CPU finding code will also be used in managed case,
So Split it out into a helper for preparation.
Signed-off-by: Dou Liyang
On Sat, 08 Sep 2018 19:00:34 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
> >
> >
> > On Sat, 08 Sep 2018 15:18:10 +0200,
> > Stefan Wahren wrote:
> > >
> > > Hi Takashi,
> > >
> > > > Takashi Iwai hat am 4. September 2018 um 17:58
On Sat, 08 Sep 2018 19:00:34 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
> >
> >
> > On Sat, 08 Sep 2018 15:18:10 +0200,
> > Stefan Wahren wrote:
> > >
> > > Hi Takashi,
> > >
> > > > Takashi Iwai hat am 4. September 2018 um 17:58
Hi Linus,
The following changes since commit a72b44a871c218e2a0580e68affa1d3528c0587a:
Merge tag 'omap-for-v4.19/fixes-v2-signed' of
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
(2018-09-01 18:22:19 -0700)
are available in the git repository at:
Hi Linus,
The following changes since commit a72b44a871c218e2a0580e68affa1d3528c0587a:
Merge tag 'omap-for-v4.19/fixes-v2-signed' of
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
(2018-09-01 18:22:19 -0700)
are available in the git repository at:
Hi,
> Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
>
>
> On Sat, 08 Sep 2018 15:18:10 +0200,
> Stefan Wahren wrote:
> >
> > Hi Takashi,
> >
> > > Takashi Iwai hat am 4. September 2018 um 17:58
> > > geschrieben:
> > >
> > >
> > > Hi,
> > >
> > > since I had an opportunity
Hi,
> Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
>
>
> On Sat, 08 Sep 2018 15:18:10 +0200,
> Stefan Wahren wrote:
> >
> > Hi Takashi,
> >
> > > Takashi Iwai hat am 4. September 2018 um 17:58
> > > geschrieben:
> > >
> > >
> > > Hi,
> > >
> > > since I had an opportunity
On 09/08/2018 06:43 AM, Masanari Iida wrote:
> This patch fixes some spelling typos found in printk messages.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> drivers/dma/ep93xx_dma.c | 6 +++---
> drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c
On 09/08/2018 06:43 AM, Masanari Iida wrote:
> This patch fixes some spelling typos found in printk messages.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> drivers/dma/ep93xx_dma.c | 6 +++---
> drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c
On Sat, 08 Sep 2018 15:18:10 +0200,
Stefan Wahren wrote:
>
> Hi Takashi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Hi,
> >
> > since I had an opportunity to play with RPi3B+ recently, I took a look
> > at the existing bcm2835-audio driver code and was
On Sat, 08 Sep 2018 15:18:10 +0200,
Stefan Wahren wrote:
>
> Hi Takashi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Hi,
> >
> > since I had an opportunity to play with RPi3B+ recently, I took a look
> > at the existing bcm2835-audio driver code and was
On Sat, 08 Sep 2018 15:25:14 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Only a few of them are really needed.
> >
> > Signed-off-by: Takashi Iwai
> > ---
> > .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15
On Sat, 08 Sep 2018 15:25:14 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Only a few of them are really needed.
> >
> > Signed-off-by: Takashi Iwai
> > ---
> > .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15
On Sat, 08 Sep 2018 15:40:41 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > The chip->audio_mutex is used basically for protecting the opened
> > stream assignment, and the prepare callback is irrelevant with it.
> >
> >
On Sat, 08 Sep 2018 15:40:41 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > The chip->audio_mutex is used basically for protecting the opened
> > stream assignment, and the prepare callback is irrelevant with it.
> >
> >
On 09/08/2018 08:54 AM, Matthew Wilcox wrote:
> On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
>> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
>>> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
- {"kmalloc-1024",
On 09/08/2018 08:54 AM, Matthew Wilcox wrote:
> On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
>> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
>>> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
- {"kmalloc-1024",
On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> > On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > > -
On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> > On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > > -
This report contains "getblk(): executed=9 bh_count=0 bh_state=0" lines.
Thus,
#syz dup: INFO: task hung in generic_file_write_iter
This report contains "getblk(): executed=9 bh_count=0 bh_state=0" lines.
Thus,
#syz dup: INFO: task hung in generic_file_write_iter
Hello,
syzbot found the following crash on:
HEAD commit:b50694381cfc Merge branch 'stable/for-linus-4.17' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166708d780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
Hello,
syzbot found the following crash on:
HEAD commit:b50694381cfc Merge branch 'stable/for-linus-4.17' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166708d780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
Marcel Holtmann wrote:
> so I have reviewed and tested this code. In addition, we have test cases for
> it in ELL (embedded linux library).
I wonder if there's any practical way to add a test for this to the keyutils
test suite. I'm guessing it's quite tricky, given the extra bits you need to
Marcel Holtmann wrote:
> so I have reviewed and tested this code. In addition, we have test cases for
> it in ELL (embedded linux library).
I wonder if there's any practical way to add a test for this to the keyutils
test suite. I'm guessing it's quite tricky, given the extra bits you need to
Tony Lindgren wrote:
> > > Looks like next-20180906 now has a regression where mounting
> > > root won't work with commit fd0002870b45 ("vfs: Implement a
> > > filesystem superblock creation/configuration context").
> >
> > Am I right in thinking you're not using any of the LSMs?
>
> Assuming
Tony Lindgren wrote:
> > > Looks like next-20180906 now has a regression where mounting
> > > root won't work with commit fd0002870b45 ("vfs: Implement a
> > > filesystem superblock creation/configuration context").
> >
> > Am I right in thinking you're not using any of the LSMs?
>
> Assuming
On Fri, Sep 7, 2018 at 9:57 PM, Kees Cook wrote:
> On Fri, Sep 7, 2018 at 9:17 AM, Tetsuo Handa
> wrote:
>> On 2018/09/08 0:29, syzbot wrote:
>>> syzbot has found a reproducer for the following crash on:
>>>
>>> HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
>>> git
On Fri, Sep 7, 2018 at 9:57 PM, Kees Cook wrote:
> On Fri, Sep 7, 2018 at 9:17 AM, Tetsuo Handa
> wrote:
>> On 2018/09/08 0:29, syzbot wrote:
>>> syzbot has found a reproducer for the following crash on:
>>>
>>> HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
>>> git
Hi,
Please Cc the watchdog maintainers. Else, I have very few comments.
On 07/09/2018 09:17:43-0600, Jeremy Gebben wrote:
> The abx804 and abx805 chips have support for a simple watchdog
> function that can trigger an external reset.
>
> Signed-off-by: Jeremy Gebben
> ---
>
Hi,
Please Cc the watchdog maintainers. Else, I have very few comments.
On 07/09/2018 09:17:43-0600, Jeremy Gebben wrote:
> The abx804 and abx805 chips have support for a simple watchdog
> function that can trigger an external reset.
>
> Signed-off-by: Jeremy Gebben
> ---
>
The /proc/pci/ implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 23c0406d8b30..28ebff2d1799
The /dev/rawX implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 28ebff2d1799..e755802cd887
The /proc/pci/ implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 23c0406d8b30..28ebff2d1799
The /dev/rawX implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 28ebff2d1799..e755802cd887
Commit aa98aa31987a ("md: move compat_ioctl handling into md.c")
already removed the COMPATIBLE_IOCTL() table entries and added
a complete implementation, but a few lines got left behind and
should also be removed here.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file
Commit aa98aa31987a ("md: move compat_ioctl handling into md.c")
already removed the COMPATIBLE_IOCTL() table entries and added
a complete implementation, but a few lines got left behind and
should also be removed here.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file
The joystick driver already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 8
1 file changed, 8 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index eb29188d1dbb..23c0406d8b30 100644
The joystick driver already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 8
1 file changed, 8 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index eb29188d1dbb..23c0406d8b30 100644
These are all handled by the random driver, so instead of listing
each ioctl, we can just use the same function to deal with both
native and compat commands.
Signed-off-by: Arnd Bergmann
---
drivers/char/random.c | 1 +
fs/compat_ioctl.c | 7 ---
2 files changed, 1 insertion(+), 7
On Tue, 4 Sep 2018 17:13:14 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol.
> This patch adds the documentation of device tree bindings for adxl372
> I2C.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
>
On Tue, 4 Sep 2018 17:13:14 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol.
> This patch adds the documentation of device tree bindings for adxl372
> I2C.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
>
These are all handled by the random driver, so instead of listing
each ioctl, we can just use the same function to deal with both
native and compat commands.
Signed-off-by: Arnd Bergmann
---
drivers/char/random.c | 1 +
fs/compat_ioctl.c | 7 ---
2 files changed, 1 insertion(+), 7
Since commit 07d106d0a33d ("vfs: fix up ENOIOCTLCMD error handling"),
we don't warn about unhandled compat-ioctl command code any more, but
just return the same error that a native file descriptor returns when
there is no handler.
This means the IGNORE_IOCTL() annotations are completely useless
Since commit 07d106d0a33d ("vfs: fix up ENOIOCTLCMD error handling"),
we don't warn about unhandled compat-ioctl command code any more, but
just return the same error that a native file descriptor returns when
there is no handler.
This means the IGNORE_IOCTL() annotations are completely useless
The SNDCTL_* and SOUND_* commands are the old OSS user interface.
I checked all the sound ioctl commands listed in fs/compat_ioctl.c
to see if we still need the translation handlers. Here is what I
found:
- sound/oss/ is (almost) gone from the kernel, this is what actually
needed all the
On Tue, 4 Sep 2018 17:12:32 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol. It
> autodetects the format being used, requiring no configuration control to
> select the format.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
>
The SNDCTL_* and SOUND_* commands are the old OSS user interface.
I checked all the sound ioctl commands listed in fs/compat_ioctl.c
to see if we still need the translation handlers. Here is what I
found:
- sound/oss/ is (almost) gone from the kernel, this is what actually
needed all the
On Tue, 4 Sep 2018 17:12:32 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol. It
> autodetects the format being used, requiring no configuration control to
> select the format.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
>
On Tue, 4 Sep 2018 17:11:31 +0300
Stefan Popa wrote:
> This patch restructures the existing adxl372 driver by adding a module for
> SPI and a header file, while the baseline module deals with the chip-logic.
>
> This is a necessary step, as this driver should support in the future
> a similar
The KD* family of ioctls is implemented in two drivers:
drivers/tty/vt and drivers/s390/char/tty3270.c. Both of them
have compat handlers for all their ioctl commands, so translation
in fs/compat_ioctl.c is never used.
Commit fb07a5f857ac ("compat_ioctl: remove all VT ioctl handling")
removed the
The KD* family of ioctls is implemented in two drivers:
drivers/tty/vt and drivers/s390/char/tty3270.c. Both of them
have compat handlers for all their ioctl commands, so translation
in fs/compat_ioctl.c is never used.
Commit fb07a5f857ac ("compat_ioctl: remove all VT ioctl handling")
removed the
On Tue, 4 Sep 2018 17:11:31 +0300
Stefan Popa wrote:
> This patch restructures the existing adxl372 driver by adding a module for
> SPI and a header file, while the baseline module deals with the chip-logic.
>
> This is a necessary step, as this driver should support in the future
> a similar
The two drivers implementing these both gained proper compat_ioctl()
handlers a long time ago with commits bb6c8d8fa9b5 ("HID: hiddev:
Add 32bit ioctl compatibilty") and ae5e49c79c05 ("HID: hidraw: add
compatibility ioctl() for 32-bit applications."), so the lists in
fs/compat_ioctl.c are no
The two drivers implementing these both gained proper compat_ioctl()
handlers a long time ago with commits bb6c8d8fa9b5 ("HID: hiddev:
Add 32bit ioctl compatibilty") and ae5e49c79c05 ("HID: hidraw: add
compatibility ioctl() for 32-bit applications."), so the lists in
fs/compat_ioctl.c are no
On Sat, 8 Sep 2018 17:59:13 +0530
Himanshu Jha wrote:
> On Sat, Sep 08, 2018 at 06:57:36PM +0800, zhong jiang wrote:
> > The iterator in for_each_set_bit is never null, therefore, remove
> > the redundant conditional judgment.
> >
> > Signed-off-by: zhong jiang
> > ---
> >
On Sat, 8 Sep 2018 17:59:13 +0530
Himanshu Jha wrote:
> On Sat, Sep 08, 2018 at 06:57:36PM +0800, zhong jiang wrote:
> > The iterator in for_each_set_bit is never null, therefore, remove
> > the redundant conditional judgment.
> >
> > Signed-off-by: zhong jiang
> > ---
> >
On 2018/09/08 22:57, Johannes Weiner wrote:
> On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
>> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and
>> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when
>> no eligible victim left"), all
>>
>>
On 2018/09/08 22:57, Johannes Weiner wrote:
> On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
>> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and
>> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when
>> no eligible victim left"), all
>>
>>
On Thu, 6 Sep 2018 14:22:06 -0700
Matthias Kaehlcke wrote:
> On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke
> > wrote:
> > > Add a channel node for the die temperature to the ADC.
> > >
> > > Signed-off-by:
On Thu, 6 Sep 2018 14:22:06 -0700
Matthias Kaehlcke wrote:
> On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke
> > wrote:
> > > Add a channel node for the die temperature to the ADC.
> > >
> > > Signed-off-by:
On Thu, 6 Sep 2018 14:04:52 -0700
Matthias Kaehlcke wrote:
> The documentation of Qualcomm's SPMI PMIC voltage ADC claims that the
> 'reg' property consists of two values, the SPMI address and the length
> of the controller's registers. However the SPMI bus to which it is added
> specifies
On Thu, 6 Sep 2018 14:04:52 -0700
Matthias Kaehlcke wrote:
> The documentation of Qualcomm's SPMI PMIC voltage ADC claims that the
> 'reg' property consists of two values, the SPMI address and the length
> of the controller's registers. However the SPMI bus to which it is added
> specifies
On Tue, 04 Sep 2018 20:23:57 +0100
Afonso Bordado wrote:
> On Fri, 2018-08-31 at 17:35 +0200, Tomasz Duszynski wrote:
> > On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
Just a quick hint to make my life
On Tue, 04 Sep 2018 20:23:57 +0100
Afonso Bordado wrote:
> On Fri, 2018-08-31 at 17:35 +0200, Tomasz Duszynski wrote:
> > On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
Just a quick hint to make my life
On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > - {"kmalloc-4096", 4096}, {"kmalloc-8192",
On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > - {"kmalloc-4096", 4096}, {"kmalloc-8192",
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 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 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 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
debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/infiniband/hw/usnic/usnic_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/usnic/usnic_debugfs.c
debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/infiniband/hw/usnic/usnic_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/usnic/usnic_debugfs.c
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
> On 2018/08/22 1:04, Johannes Weiner wrote:
> > When the memcg OOM killer runs out of killable tasks, it currently
> > prints a WARN with no further OOM context. This has caused some user
> > confusion.
> >
> > Warnings indicate a
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
> On 2018/08/22 1:04, Johannes Weiner wrote:
> > When the memcg OOM killer runs out of killable tasks, it currently
> > prints a WARN with no further OOM context. This has caused some user
> > confusion.
> >
> > Warnings indicate a
I, Mikhail Fridman have selected you specifically as one of my
beneficiaries for my Charitable Donation,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response.
Best Regards,
Mikhail Fridman.
I, Mikhail Fridman have selected you specifically as one of my
beneficiaries for my Charitable Donation,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response.
Best Regards,
Mikhail Fridman.
On Thu, 6 Sep 2018 15:19:29 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks a lot for the review. Please see my response inline.
Hi Manish,
Just one thing to think about. (and I'm not that great about this
myself :) Please look to crop out irrelevant text. It saves
time when people are
On Thu, 6 Sep 2018 15:19:29 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks a lot for the review. Please see my response inline.
Hi Manish,
Just one thing to think about. (and I'm not that great about this
myself :) Please look to crop out irrelevant text. It saves
time when people are
This patch fixes some spelling typos found in printk messages.
Signed-off-by: Masanari Iida
---
drivers/dma/ep93xx_dma.c | 6 +++---
drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +-
drivers/gpu/drm/drm_kms_helper_common.c| 2 +-
This patch fixes some spelling typos found in printk messages.
Signed-off-by: Masanari Iida
---
drivers/dma/ep93xx_dma.c | 6 +++---
drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +-
drivers/gpu/drm/drm_kms_helper_common.c| 2 +-
On Thu, 6 Sep 2018 13:27:34 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks for the review!
>
> > -Original Message-
> > From: Jonathan Cameron [mailto:ji...@kernel.org]
> > Sent: Sunday, September 2, 2018 11:45 PM
> > To: Manish Narani
> > Cc: knaac...@gmx.de; l...@metafoo.de;
On Thu, 6 Sep 2018 13:27:34 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks for the review!
>
> > -Original Message-
> > From: Jonathan Cameron [mailto:ji...@kernel.org]
> > Sent: Sunday, September 2, 2018 11:45 PM
> > To: Manish Narani
> > Cc: knaac...@gmx.de; l...@metafoo.de;
debugfs_remove_recursive has taken IS_ERR_OR_NULL into account. So just
remove the condition check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/md/bcache/debug.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/debug.c
debugfs_remove_recursive has taken IS_ERR_OR_NULL into account. So just
remove the condition check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/md/bcache/debug.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/debug.c
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> The chip->audio_mutex is used basically for protecting the opened
> stream assignment, and the prepare callback is irrelevant with it.
>
> Signed-off-by: Takashi Iwai
> ---
>
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> The chip->audio_mutex is used basically for protecting the opened
> stream assignment, and the prepare callback is irrelevant with it.
>
> Signed-off-by: Takashi Iwai
> ---
>
On 2018/08/22 1:04, Johannes Weiner wrote:
> When the memcg OOM killer runs out of killable tasks, it currently
> prints a WARN with no further OOM context. This has caused some user
> confusion.
>
> Warnings indicate a kernel problem. In a reported case, however, the
> situation was triggered by
On 2018/08/22 1:04, Johannes Weiner wrote:
> When the memcg OOM killer runs out of killable tasks, it currently
> prints a WARN with no further OOM context. This has caused some user
> confusion.
>
> Warnings indicate a kernel problem. In a reported case, however, the
> situation was triggered by
On 09/08/18 at 02:10pm, Thomas Gleixner wrote:
> On Wed, 29 Aug 2018, Baoquan He wrote:
>
> > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
> > initial size of the direct mapping region. This is right in the
> > old code where __PHYSICAL_MASK_SHIFT was equal to
On 09/08/18 at 02:10pm, Thomas Gleixner wrote:
> On Wed, 29 Aug 2018, Baoquan He wrote:
>
> > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
> > initial size of the direct mapping region. This is right in the
> > old code where __PHYSICAL_MASK_SHIFT was equal to
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> Only a few of them are really needed.
>
> Signed-off-by: Takashi Iwai
> ---
> .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15 ---
I think this patch and patch #23 could be merge in case a new series
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> Only a few of them are really needed.
>
> Signed-off-by: Takashi Iwai
> ---
> .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15 ---
I think this patch and patch #23 could be merge in case a new series
Some mtd drivers like physmap variants have support for concatenating
multiple mtd devices, but there is no generic way to define such a
concat device from within the device tree.
This is useful for some SoC boards that use multiple flash chips as
memory banks of a single mtd device, with
Some mtd drivers like physmap variants have support for concatenating
multiple mtd devices, but there is no generic way to define such a
concat device from within the device tree.
This is useful for some SoC boards that use multiple flash chips as
memory banks of a single mtd device, with
101 - 200 of 352 matches
Mail list logo
