System may crash after unloading ipmi_si.ko module
because a timer may remain and fire after the module cleaned up resources.
cleanup_one_si() contains the following processing.
/*
* Make sure that interrupts, the timer and the thread are
* stopped and will not run
System may crash after unloading ipmi_si.ko module
because a timer may remain and fire after the module cleaned up resources.
cleanup_one_si() contains the following processing.
/*
* Make sure that interrupts, the timer and the thread are
* stopped and will not run
Some functions from refcount_t API provide different
memory ordering guarantees that their atomic counterparts.
This adds a document outlining these differences.
Signed-off-by: Elena Reshetova
---
Documentation/refcount-vs-atomic.txt | 124
Some functions from refcount_t API provide different
memory ordering guarantees that their atomic counterparts.
This adds a document outlining these differences.
Signed-off-by: Elena Reshetova
---
Documentation/refcount-vs-atomic.txt | 124 +++
1 file changed,
Hi,
Thanks for Guenter's review and detail comments.
Please help to apply this patch if there is no any other comments.
Best regards,
Eric Long
On Fri, Nov 10, 2017 at 01:00:32PM -0800, Guenter Roeck wrote:
> On Mon, Nov 06, 2017 at 10:46:28AM +0800, Eric Long wrote:
> > This patch adds the
Hi,
Thanks for Guenter's review and detail comments.
Please help to apply this patch if there is no any other comments.
Best regards,
Eric Long
On Fri, Nov 10, 2017 at 01:00:32PM -0800, Guenter Roeck wrote:
> On Mon, Nov 06, 2017 at 10:46:28AM +0800, Eric Long wrote:
> > This patch adds the
Changes in v2:
- typos and english are fixed based on Randy Dunlap's
proof reading
- structure of document improved:
* definitions now in the beginning
* confusing examples removed
* less redundancy overall and more up-to-the-point text
- definitions try to follow LKMM
Changes in v2:
- typos and english are fixed based on Randy Dunlap's
proof reading
- structure of document improved:
* definitions now in the beginning
* confusing examples removed
* less redundancy overall and more up-to-the-point text
- definitions try to follow LKMM
On Wed, Nov 15, 2017 at 08:43:58AM +0100, Ingo Molnar wrote:
>
> * Rafael J. Wysocki wrote:
>
> > On Wednesday, November 15, 2017 1:06:12 AM CET Linus Torvalds wrote:
> > > On Tue, Nov 14, 2017 at 4:04 PM, Linus Torvalds
> > > wrote:
> > > >
On Wed, Nov 15, 2017 at 08:43:58AM +0100, Ingo Molnar wrote:
>
> * Rafael J. Wysocki wrote:
>
> > On Wednesday, November 15, 2017 1:06:12 AM CET Linus Torvalds wrote:
> > > On Tue, Nov 14, 2017 at 4:04 PM, Linus Torvalds
> > > wrote:
> > > > On Tue, Nov 14, 2017 at 3:53 PM, Thomas Gleixner
>
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> Even with the introduced vchan_synchronize() we can face race when
> terminating a cyclic transfer.
>
> If the terminate_all is called after the interrupt handler called
> vchan_cyclic_callback(), but before the
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> Even with the introduced vchan_synchronize() we can face race when
> terminating a cyclic transfer.
>
> If the terminate_all is called after the interrupt handler called
> vchan_cyclic_callback(), but before the vchan_complete tasklet is
* Linus Torvalds wrote:
> On Tue, Nov 14, 2017 at 1:48 AM, Borislav Petkov wrote:
> >
> > Just did 2 suspend cycles (once to RAM and once to disk) on my x230
> > with your tree from right now and it looks ok so far. So it could be
> > machine- and
* Linus Torvalds wrote:
> On Tue, Nov 14, 2017 at 1:48 AM, Borislav Petkov wrote:
> >
> > Just did 2 suspend cycles (once to RAM and once to disk) on my x230
> > with your tree from right now and it looks ok so far. So it could be
> > machine- and config-specific...
>
> .. and it's not
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> To avoid race with vchan_complete, use the race free way to terminate
> running transfer.
>
> Implement the device_synchronize callback to make sure that the terminated
> descriptor is freed.
>
> CC: Linus Walleij
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> To avoid race with vchan_complete, use the race free way to terminate
> running transfer.
>
> Implement the device_synchronize callback to make sure that the terminated
> descriptor is freed.
>
> CC: Linus Walleij
> Signed-off-by: Peter
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> The vchan_vdesc_fini() can be used to free or reuse a given descriptor
> after it has been marked as completed.
>
> Signed-off-by: Peter Ujfalusi
Reviewed-by: Linus Walleij
On Tue, Nov 14, 2017 at 3:32 PM, Peter Ujfalusi wrote:
> The vchan_vdesc_fini() can be used to free or reuse a given descriptor
> after it has been marked as completed.
>
> Signed-off-by: Peter Ujfalusi
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
Hi Jaegeuk,
On 2017/11/14 13:12, Jaegeuk Kim wrote:
> This patch shows # of dirty pages and # of hidden quota files.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/debug.c | 11 +++
> fs/f2fs/f2fs.h | 10 --
> 2 files changed, 19 insertions(+), 2
Hi Jaegeuk,
On 2017/11/14 13:12, Jaegeuk Kim wrote:
> This patch shows # of dirty pages and # of hidden quota files.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/debug.c | 11 +++
> fs/f2fs/f2fs.h | 10 --
> 2 files changed, 19 insertions(+), 2 deletions(-)
>
> diff --git
Am 15.11.2017 07:29 schrieb Greg KH:
On Tue, Nov 14, 2017 at 10:50:37AM +0100, Martin Kepplinger wrote:
A few years ago the FSF moved and "59 Temple Place" is wrong. Having
this
still in our source files feels old and unmaintained.
Let's take the license statement serious and not confuse
Am 15.11.2017 07:29 schrieb Greg KH:
On Tue, Nov 14, 2017 at 10:50:37AM +0100, Martin Kepplinger wrote:
A few years ago the FSF moved and "59 Temple Place" is wrong. Having
this
still in our source files feels old and unmaintained.
Let's take the license statement serious and not confuse
Hi Matthieu
On 14 November 2017 at 21:03, Mathieu Desnoyers
wrote:
> This new cpu_opv system call executes a vector of operations on behalf
> of user-space on a specific CPU with preemption disabled. It is inspired
> from readv() and writev() system calls which
Hi Matthieu
On 14 November 2017 at 21:03, Mathieu Desnoyers
wrote:
> This new cpu_opv system call executes a vector of operations on behalf
> of user-space on a specific CPU with preemption disabled. It is inspired
> from readv() and writev() system calls which take a "struct iovec" array
> as
* Rafael J. Wysocki wrote:
> On Wednesday, November 15, 2017 1:06:12 AM CET Linus Torvalds wrote:
> > On Tue, Nov 14, 2017 at 4:04 PM, Linus Torvalds
> > wrote:
> > > On Tue, Nov 14, 2017 at 3:53 PM, Thomas Gleixner
> > >
* Rafael J. Wysocki wrote:
> On Wednesday, November 15, 2017 1:06:12 AM CET Linus Torvalds wrote:
> > On Tue, Nov 14, 2017 at 4:04 PM, Linus Torvalds
> > wrote:
> > > On Tue, Nov 14, 2017 at 3:53 PM, Thomas Gleixner
> > > wrote:
> > >> Current head + Raphaels patch:
> > >>
> > >> real
On Tue, Nov 14, 2017 at 12:39 PM, Arnd Bergmann wrote:
> linux/gpio/consumer.h is a bit odd, it contains definitions for a number
> of the advanced gpio interfaces, in variants for both gpiolib-based
> platforms and those not using gpiolib.
>
> The file gets included implicitly by
On Tue, Nov 14, 2017 at 12:39 PM, Arnd Bergmann wrote:
> linux/gpio/consumer.h is a bit odd, it contains definitions for a number
> of the advanced gpio interfaces, in variants for both gpiolib-based
> platforms and those not using gpiolib.
>
> The file gets included implicitly by linux/gpio.h,
On 12 November 2017 at 01:42, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Add helper routines to find and return a suitable subsystem callback
> during the "noirq" phases of system suspend/resume (or analogous)
> transitions as well as
On 12 November 2017 at 01:42, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Add helper routines to find and return a suitable subsystem callback
> during the "noirq" phases of system suspend/resume (or analogous)
> transitions as well as during the "late" phase of system suspend and
>
bus access read/write events are not supported in A73, based on the
Cortex-A73 TRM r0p2, section 11.9 Events (pages 11-457 to 11-460).
Fixes: 5561b6c5e981 "arm64: perf: add support for Cortex-A73"
Signed-off-by: Xu YiPing
---
arch/arm64/kernel/perf_event.c | 6 --
1
bus access read/write events are not supported in A73, based on the
Cortex-A73 TRM r0p2, section 11.9 Events (pages 11-457 to 11-460).
Fixes: 5561b6c5e981 "arm64: perf: add support for Cortex-A73"
Signed-off-by: Xu YiPing
---
arch/arm64/kernel/perf_event.c | 6 --
1 file changed, 6
On Tue, Nov 14, 2017 at 11:13:43PM -0800, Bjorn Andersson wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This adds a new optional operator that LED class drivers can implement
> if they
On Tue, Nov 14, 2017 at 11:13:43PM -0800, Bjorn Andersson wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This adds a new optional operator that LED class drivers can implement
> if they
* Josef Bacik wrote:
> > > Then 'not crashing kernel' requirement will be preserved.
> > > btrfs or whatever else we will be testing with override_return
> > > will be functioning in 'stress test' mode and if bpf program
> > > is not careful and returns error all the time
* Josef Bacik wrote:
> > > Then 'not crashing kernel' requirement will be preserved.
> > > btrfs or whatever else we will be testing with override_return
> > > will be functioning in 'stress test' mode and if bpf program
> > > is not careful and returns error all the time then one particular
>
[Adding more people and alsa-devel to Cc]
On Wed, 15 Nov 2017 03:40:09 +0100,
Linus Torvalds wrote:
>
> On Tue, Nov 14, 2017 at 6:51 AM, Takashi Iwai wrote:
> >
> > please pull sound updates for v4.15-rc1 from:
>
> Hmm. Making "oldconfig" on my laptop with this, my
>
[Adding more people and alsa-devel to Cc]
On Wed, 15 Nov 2017 03:40:09 +0100,
Linus Torvalds wrote:
>
> On Tue, Nov 14, 2017 at 6:51 AM, Takashi Iwai wrote:
> >
> > please pull sound updates for v4.15-rc1 from:
>
> Hmm. Making "oldconfig" on my laptop with this, my
> SND_SOC_INTEL_SKYLAKE went
From: Jacob Chen
rk3288 have a Embedded 13M ISP and MIPI-CSI2 interface.
Signed-off-by: Jacob Chen
---
arch/arm/boot/dts/rk3288.dtsi | 24
1 file changed, 24 insertions(+)
diff --git
From: Jacob Chen
rk3288 have a Embedded 13M ISP and MIPI-CSI2 interface.
Signed-off-by: Jacob Chen
---
arch/arm/boot/dts/rk3288.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index
From: Shunqian Zheng
rk3399 have two ISP, but we havn't test isp1, so just add isp0 at present.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 26
From: Shunqian Zheng
rk3399 have two ISP, but we havn't test isp1, so just add isp0 at present.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 26 ++
1 file changed, 26 insertions(+)
diff --git
From: Jeffy Chen
Add the header for userspace
Signed-off-by: Jeffy Chen
Signed-off-by: Jacob Chen
---
include/uapi/linux/rkisp1-config.h | 554 +
1 file changed, 554
From: Jeffy Chen
Add the header for userspace
Signed-off-by: Jeffy Chen
Signed-off-by: Jacob Chen
---
include/uapi/linux/rkisp1-config.h | 554 +
1 file changed, 554 insertions(+)
create mode 100644 include/uapi/linux/rkisp1-config.h
diff --git
From: Shunqian Zheng
Add the Rockchip ISP1 specific processing parameter format
V4L2_META_FMT_RK_ISP1_PARAMS and metadata format
V4L2_META_FMT_RK_ISP1_STAT_3A for 3A.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
From: Shunqian Zheng
Add the Rockchip ISP1 specific processing parameter format
V4L2_META_FMT_RK_ISP1_PARAMS and metadata format
V4L2_META_FMT_RK_ISP1_STAT_3A for 3A.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
drivers/media/v4l2-core/v4l2-ioctl.c | 2 ++
It will be more helpful to add some tracepoints to track RTC actions when
debugging RTC driver. Below sample is that we set/read the RTC time, then
set 2 alarms, so we can see the trace logs:
set/read RTC time:
kworker/1:1-586 [001] 21.826112: rtc_set_time: 2017-11-10 08:13:00 UTC
It will be more helpful to add some tracepoints to track RTC actions when
debugging RTC driver. Below sample is that we set/read the RTC time, then
set 2 alarms, so we can see the trace logs:
set/read RTC time:
kworker/1:1-586 [001] 21.826112: rtc_set_time: 2017-11-10 08:13:00 UTC
This patch series add a ISP(Camera) v4l2 driver for rockchip rk3288/rk3399 SoC.
TODO:
- Thomas is rewriting the binding code between isp, phy, sensors, i hope we
could get suggestions.
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/768633/2
rules:
This patch series add a ISP(Camera) v4l2 driver for rockchip rk3288/rk3399 SoC.
TODO:
- Thomas is rewriting the binding code between isp, phy, sensors, i hope we
could get suggestions.
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/768633/2
rules:
From: Shunqian Zheng
Add the Rockchip ISP1 specific processing parameter format
V4L2_META_FMT_RK_ISP1_PARAMS and metadata format
V4L2_META_FMT_RK_ISP1_STAT_3A for 3A.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
From: Shunqian Zheng
Add the Rockchip ISP1 specific processing parameter format
V4L2_META_FMT_RK_ISP1_PARAMS and metadata format
V4L2_META_FMT_RK_ISP1_STAT_3A for 3A.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
drivers/media/v4l2-core/v4l2-ioctl.c | 2 ++
Hi,
On 11/14/2017 03:28 PM, Felipe Balbi wrote:
> Hi,
>
> Mathias Nyman writes:
>>> +static int dbc_buf_alloc(struct dbc_buf *db, unsigned int size)
>>> +{
>>> + db->buf_buf = kzalloc(size, GFP_KERNEL);
>>> + if (!db->buf_buf)
>>> + return -ENOMEM;
Hi,
On 11/14/2017 03:28 PM, Felipe Balbi wrote:
> Hi,
>
> Mathias Nyman writes:
>>> +static int dbc_buf_alloc(struct dbc_buf *db, unsigned int size)
>>> +{
>>> + db->buf_buf = kzalloc(size, GFP_KERNEL);
>>> + if (!db->buf_buf)
>>> + return -ENOMEM;
>>> +
>>> + db->buf_size =
On Tue 14 Nov 22:58 PST 2017, Christophe JAILLET wrote:
> In case of error returned by 'q6v5_xfer_mem_ownership', we must free
> some resources before returning.
>
> In 'q6v5_mpss_init_image()', add a new label to undo a previous
> 'dma_alloc_attrs()'.
> In 'q6v5_mpss_load()', re-use the already
On Tue 14 Nov 22:58 PST 2017, Christophe JAILLET wrote:
> In case of error returned by 'q6v5_xfer_mem_ownership', we must free
> some resources before returning.
>
> In 'q6v5_mpss_init_image()', add a new label to undo a previous
> 'dma_alloc_attrs()'.
> In 'q6v5_mpss_load()', re-use the already
[...]
>>
>> When pm_runtime_set_suspended(dev) is called, dev's child device may
>> still be runtime PM enabled and active.
>> I was suggesting to add a check for this scenario, to see if dev's
>> child device is runtime PM is enabled, as and additional constraint
>> before deciding to return an
[...]
>>
>> When pm_runtime_set_suspended(dev) is called, dev's child device may
>> still be runtime PM enabled and active.
>> I was suggesting to add a check for this scenario, to see if dev's
>> child device is runtime PM is enabled, as and additional constraint
>> before deciding to return an
This series introduces a generic pattern interface in the LED class and
a driver for the Qualcomm Light Pulse Generator.
Bjorn Andersson (3):
leds: core: Introduce generic pattern interface
leds: Add driver for Qualcomm LPG
DT: leds: Add Qualcomm Light Pulse Generator binding
This series introduces a generic pattern interface in the LED class and
a driver for the Qualcomm Light Pulse Generator.
Bjorn Andersson (3):
leds: core: Introduce generic pattern interface
leds: Add driver for Qualcomm LPG
DT: leds: Add Qualcomm Light Pulse Generator binding
This adds the binding document describing the three hardware blocks
related to the Light Pulse Generator found in a wide range of Qualcomm
PMICs.
Signed-off-by: Bjorn Andersson
---
Changes since v2:
- Squashed all things into one node
- Removed quirks from the
The Light Pulse Generator (LPG) is a PWM-block found in a wide range of
PMICs from Qualcomm. It can operate on fixed parameters or based on a
lookup-table, altering the duty cycle over time - which provides the
means for e.g. hardware assisted transitions of LED brightness.
Signed-off-by: Bjorn
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class drivers can implement
if they support such functionality as well as a new device attribute to
configure the
This adds the binding document describing the three hardware blocks
related to the Light Pulse Generator found in a wide range of Qualcomm
PMICs.
Signed-off-by: Bjorn Andersson
---
Changes since v2:
- Squashed all things into one node
- Removed quirks from the binding, compatible implies number
The Light Pulse Generator (LPG) is a PWM-block found in a wide range of
PMICs from Qualcomm. It can operate on fixed parameters or based on a
lookup-table, altering the duty cycle over time - which provides the
means for e.g. hardware assisted transitions of LED brightness.
Signed-off-by: Bjorn
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class drivers can implement
if they support such functionality as well as a new device attribute to
configure the
On 11/14/2017 07:44 PM, Matthew Wilcox wrote:
> On Mon, Nov 13, 2017 at 02:46:25PM -0800, Dave Hansen wrote:
>> On 11/13/2017 02:20 PM, Dave Hansen wrote:
>>> On 11/09/2017 05:09 PM, Tycho Andersen wrote:
which I guess is from the additional flags in grow_dev_page() somewhere
down
On 11/14/2017 07:44 PM, Matthew Wilcox wrote:
> On Mon, Nov 13, 2017 at 02:46:25PM -0800, Dave Hansen wrote:
>> On 11/13/2017 02:20 PM, Dave Hansen wrote:
>>> On 11/09/2017 05:09 PM, Tycho Andersen wrote:
which I guess is from the additional flags in grow_dev_page() somewhere
down
In case of error returned by 'q6v5_xfer_mem_ownership', we must free
some resources before returning.
In 'q6v5_mpss_init_image()', add a new label to undo a previous
'dma_alloc_attrs()'.
In 'q6v5_mpss_load()', re-use the already existing error handling code to
undo a previous
In case of error returned by 'q6v5_xfer_mem_ownership', we must free
some resources before returning.
In 'q6v5_mpss_init_image()', add a new label to undo a previous
'dma_alloc_attrs()'.
In 'q6v5_mpss_load()', re-use the already existing error handling code to
undo a previous
On 11/15/17 at 01:47pm, Baoquan He wrote:
> Hi Dave,
>
> Thanks for your effort to push this into upstream. While I have one
> concern, please see the inline comments.
>
> On 10/24/17 at 01:31pm, Dave Young wrote:
> > Now crashkernel=X will fail if there's not enough memory at low region
> >
On 11/15/17 at 01:47pm, Baoquan He wrote:
> Hi Dave,
>
> Thanks for your effort to push this into upstream. While I have one
> concern, please see the inline comments.
>
> On 10/24/17 at 01:31pm, Dave Young wrote:
> > Now crashkernel=X will fail if there's not enough memory at low region
> >
On 2017/11/15 05:54, r...@redhat.com wrote:
From: Rik van Riel
Currently, every time a VCPU is scheduled out, the host kernel will
first save the guest FPU/xstate context, then load the qemu userspace
FPU context, only to then immediately save the qemu userspace FPU
context
On 2017/11/15 05:54, r...@redhat.com wrote:
From: Rik van Riel
Currently, every time a VCPU is scheduled out, the host kernel will
first save the guest FPU/xstate context, then load the qemu userspace
FPU context, only to then immediately save the qemu userspace FPU
context back to memory.
- On Nov 14, 2017, at 11:38 PM, Stephen Rothwell s...@canb.auug.org.au
wrote:
> Hi Mathieu,
>
> On Wed, 15 Nov 2017 01:22:04 + (UTC) Mathieu Desnoyers
> wrote:
>>
>> - On Nov 14, 2017, at 7:15 PM, Stephen Rothwell s...@canb.auug.org.au
>> wrote:
>>
- On Nov 14, 2017, at 11:38 PM, Stephen Rothwell s...@canb.auug.org.au
wrote:
> Hi Mathieu,
>
> On Wed, 15 Nov 2017 01:22:04 + (UTC) Mathieu Desnoyers
> wrote:
>>
>> - On Nov 14, 2017, at 7:15 PM, Stephen Rothwell s...@canb.auug.org.au
>> wrote:
>>
>> > On Tue, 14 Nov 2017
On Tue, Nov 14, 2017 at 11:48 AM, Dan Carpenter
wrote:
> On Tue, Nov 14, 2017 at 11:33:20AM +0200, Gilad Ben-Yossef wrote:
>> On Mon, Nov 13, 2017 at 8:33 PM, Dan Carpenter
>> wrote:
>> > These cleanups look nice. Thanks.
>> >
>> > I hope you
On Tue, Nov 14, 2017 at 11:48 AM, Dan Carpenter
wrote:
> On Tue, Nov 14, 2017 at 11:33:20AM +0200, Gilad Ben-Yossef wrote:
>> On Mon, Nov 13, 2017 at 8:33 PM, Dan Carpenter
>> wrote:
>> > These cleanups look nice. Thanks.
>> >
>> > I hope you do a mass remove of likely/unlikely in a patch
There is a regression of commit 4a646580f793 ("Input: ALPS - fix
two-finger scroll breakage"), ALPS device fails with log:
psmouse serio1: alps: Rejected trackstick packet from non DualPoint device
ALPS device with id "74 03 28" report OTP[0] data 0xCE after
commit 4a646580f793, after restore
There is a regression of commit 4a646580f793 ("Input: ALPS - fix
two-finger scroll breakage"), ALPS device fails with log:
psmouse serio1: alps: Rejected trackstick packet from non DualPoint device
ALPS device with id "74 03 28" report OTP[0] data 0xCE after
commit 4a646580f793, after restore
- On Nov 14, 2017, at 11:12 PM, Andy Lutomirski l...@amacapital.net wrote:
>> On Nov 14, 2017, at 1:32 PM, Mathieu Desnoyers
>>
>> wrote:
>>
>> - On Nov 14, 2017, at 4:15 PM, Andy Lutomirski l...@amacapital.net wrote:
>>
>>
>> One thing I kept however
- On Nov 14, 2017, at 11:12 PM, Andy Lutomirski l...@amacapital.net wrote:
>> On Nov 14, 2017, at 1:32 PM, Mathieu Desnoyers
>>
>> wrote:
>>
>> - On Nov 14, 2017, at 4:15 PM, Andy Lutomirski l...@amacapital.net wrote:
>>
>>
>> One thing I kept however that diverge from your
On Tue, Nov 14, 2017 at 10:50:37AM +0100, Martin Kepplinger wrote:
> A few years ago the FSF moved and "59 Temple Place" is wrong. Having this
> still in our source files feels old and unmaintained.
>
> Let's take the license statement serious and not confuse users.
>
> As
On Tue, Nov 14, 2017 at 10:50:37AM +0100, Martin Kepplinger wrote:
> A few years ago the FSF moved and "59 Temple Place" is wrong. Having this
> still in our source files feels old and unmaintained.
>
> Let's take the license statement serious and not confuse users.
>
> As
On Tue, Nov 14, 2017 at 4:56 PM, Minchan Kim wrote:
> On Tue, Nov 14, 2017 at 06:37:42AM +0900, Tetsuo Handa wrote:
>> When shrinker_rwsem was introduced, it was assumed that
>> register_shrinker()/unregister_shrinker() are really unlikely paths
>> which are called during
On Tue, Nov 14, 2017 at 4:56 PM, Minchan Kim wrote:
> On Tue, Nov 14, 2017 at 06:37:42AM +0900, Tetsuo Handa wrote:
>> When shrinker_rwsem was introduced, it was assumed that
>> register_shrinker()/unregister_shrinker() are really unlikely paths
>> which are called during initialization and tear
Kirill Tkhai writes:
> Curently mutex is used to protect pernet operations list. It makes
> cleanup_net() to execute ->exit methods of the same operations set,
> which was used on the time of ->init, even after net namespace is
> unlinked from net_namespace_list.
>
> But
Kirill Tkhai writes:
> Curently mutex is used to protect pernet operations list. It makes
> cleanup_net() to execute ->exit methods of the same operations set,
> which was used on the time of ->init, even after net namespace is
> unlinked from net_namespace_list.
>
> But the problem is it's need
Add support for USB3 snooping by asserting bits
in register DWC3_GSBUSCFG0 for data and descriptor.
Signed-off-by: Changming Huang
Signed-off-by: Rajesh Bhagat
Signed-off-by: Ran Wang
---
drivers/usb/dwc3/core.c | 24
Add support for USB3 snooping by asserting bits
in register DWC3_GSBUSCFG0 for data and descriptor.
Signed-off-by: Changming Huang
Signed-off-by: Rajesh Bhagat
Signed-off-by: Ran Wang
---
drivers/usb/dwc3/core.c | 24
drivers/usb/dwc3/core.h | 10 ++
2 files
On Tue, 14 Nov 2017, Masahiro Yamada wrote:
> Hi Julia,
>
>
> 2017-11-14 18:07 GMT+09:00 Julia Lawall :
> >> coccicheck failed
> >> $ cat cocci-debug.txt
> >> /home/masahiro/bin/spatch -D report --no-show-diff --very-quiet
> >> --cocci-file
On Tue, 14 Nov 2017, Masahiro Yamada wrote:
> Hi Julia,
>
>
> 2017-11-14 18:07 GMT+09:00 Julia Lawall :
> >> coccicheck failed
> >> $ cat cocci-debug.txt
> >> /home/masahiro/bin/spatch -D report --no-show-diff --very-quiet
> >> --cocci-file scripts/coccinelle/null/badzero.cocci --dir . -I
> >>
Hi, Brian,
thanks for your quick fix, as it is in merge window right now, I will
queue it for for next -rc2.
thanks,
rui
On Tue, 2017-11-14 at 10:50 -0700, Brian Bian wrote:
> I have submitted a patch to suppress such messages. The INT3400
> driver
> currently handles 0x83
Hi, Brian,
thanks for your quick fix, as it is in merge window right now, I will
queue it for for next -rc2.
thanks,
rui
On Tue, 2017-11-14 at 10:50 -0700, Brian Bian wrote:
> I have submitted a patch to suppress such messages. The INT3400
> driver
> currently handles 0x83
On Sun 12 Nov 09:17 PST 2017, Randy Dunlap wrote:
> [44098.635339] qcom_glink_native: module license 'unspecified' taints kernel.
Thanks for reporting this.
Regards,
Bjorn
On Sun 12 Nov 09:17 PST 2017, Randy Dunlap wrote:
> [44098.635339] qcom_glink_native: module license 'unspecified' taints kernel.
Thanks for reporting this.
Regards,
Bjorn
On 2017-11-08 16:04, Vasily Averin wrote:
> On 2017-11-08 15:09, Alexander Shishkin wrote:
>> On Mon, Nov 06, 2017 at 09:22:18AM +0300, Vasily Averin wrote:
>>> Fixes: commit e422267322cd ("perf: Add PERF_RECORD_NAMESPACES to include
>>> namespaces related info")
>>> Signed-off-by: Vasily Averin
On 2017-11-08 16:04, Vasily Averin wrote:
> On 2017-11-08 15:09, Alexander Shishkin wrote:
>> On Mon, Nov 06, 2017 at 09:22:18AM +0300, Vasily Averin wrote:
>>> Fixes: commit e422267322cd ("perf: Add PERF_RECORD_NAMESPACES to include
>>> namespaces related info")
>>> Signed-off-by: Vasily Averin
Hi Dave,
Thanks for your effort to push this into upstream. While I have one
concern, please see the inline comments.
On 10/24/17 at 01:31pm, Dave Young wrote:
> Now crashkernel=X will fail if there's not enough memory at low region
> (below 896M) when trying to reserve large memory size. One
Hi Dave,
Thanks for your effort to push this into upstream. While I have one
concern, please see the inline comments.
On 10/24/17 at 01:31pm, Dave Young wrote:
> Now crashkernel=X will fail if there's not enough memory at low region
> (below 896M) when trying to reserve large memory size. One
1 - 100 of 1876 matches
Mail list logo