A failure in validate_xmit_skb_list() triggered an unconditional call
to dev_requeue_skb with skb=NULL. This slowly grows the queue
discipline's qlen count until all traffic through the queue stops.
Fixes: 55a93b3ea780 ("qdisc: validate skb without holding lock")
Signed-off-by: Lars Persson
A failure in validate_xmit_skb_list() triggered an unconditional call
to dev_requeue_skb with skb=NULL. This slowly grows the queue
discipline's qlen count until all traffic through the queue stops.
Fixes: 55a93b3ea780 ("qdisc: validate skb without holding lock")
Signed-off-by: Lars Persson
---
On 2016/04/06 at 17:30, Peter Zijlstra wrote:
> On Sat, Apr 02, 2016 at 06:14:28PM +0800, Xunlei Pang wrote:
>> Your proposal is very nice!
>>
>> At the sched_init() stage we only have one (to be "idle") task and with irq
>> disabled,
>> no scheduling will happen, and the cpu_possible_mask was
On 2016/04/06 at 17:30, Peter Zijlstra wrote:
> On Sat, Apr 02, 2016 at 06:14:28PM +0800, Xunlei Pang wrote:
>> Your proposal is very nice!
>>
>> At the sched_init() stage we only have one (to be "idle") task and with irq
>> disabled,
>> no scheduling will happen, and the cpu_possible_mask was
If mutliple tasks contest try_to_take_rt_mutex(), it should
let the high-priority task acquire the lock, but it misses
the deadline tasks in the following condition:
if (task->prio >= rt_mutex_top_waiter(lock)->prio)
return 0;
Deadline tasks all have "-1" prio, so above logic will
If mutliple tasks contest try_to_take_rt_mutex(), it should
let the high-priority task acquire the lock, but it misses
the deadline tasks in the following condition:
if (task->prio >= rt_mutex_top_waiter(lock)->prio)
return 0;
Deadline tasks all have "-1" prio, so above logic will
On Fri 2016-03-25 14:34:52, Josh Poimboeuf wrote:
> This is a horrible way to detect whether a task has been preempted.
> Come up with something better: task flag? or is there already an
> existing mechanism?
What about using kallsyms_lookup_size_offset() to check the address.
It is more
On Fri 2016-03-25 14:34:52, Josh Poimboeuf wrote:
> This is a horrible way to detect whether a task has been preempted.
> Come up with something better: task flag? or is there already an
> existing mechanism?
What about using kallsyms_lookup_size_offset() to check the address.
It is more
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patchset adds gpio-signaled acpi events support for power button on
> hisilicon
> D02 board.
>
> The three patches respectively:
> - remove name from dwapb_port_property
> - convert device node to fwnode
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patchset adds gpio-signaled acpi events support for power button on
> hisilicon
> D02 board.
>
> The three patches respectively:
> - remove name from dwapb_port_property
> - convert device node to fwnode
> - add
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patch converts device node to fwnode for dwapb driver, so
> as to provide a unified fwnode for DT and ACPI bindings.
>
> Acked-by: Andy Shevchenko
> Signed-off-by: qiujiang
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patch converts device node to fwnode for dwapb driver, so
> as to provide a unified fwnode for DT and ACPI bindings.
>
> Acked-by: Andy Shevchenko
> Signed-off-by: qiujiang
> static struct dwapb_platform_data *
>
On 2016년 03월 30일 16:12, Minchan Kim wrote:
This patch introduces run-time migration feature for zspage.
To begin with, it supports only head page migration for
easy review(later patches will support tail page migration).
For migration, it supports three functions
* zs_page_isolate
It isolates
On 2016년 03월 30일 16:12, Minchan Kim wrote:
This patch introduces run-time migration feature for zspage.
To begin with, it supports only head page migration for
easy review(later patches will support tail page migration).
For migration, it supports three functions
* zs_page_isolate
It isolates
A crash happened while I'm playing with deadline PI rtmutex.
BUG: unable to handle kernel NULL pointer dereference at 0018
IP: [] rt_mutex_get_top_task+0x1f/0x30
PGD 232a75067 PUD 230947067 PMD 0
Oops: [#1] SMP
CPU: 1 PID: 10994 Comm: a.out Not tainted
A crash happened while I'm playing with deadline PI rtmutex.
BUG: unable to handle kernel NULL pointer dereference at 0018
IP: [] rt_mutex_get_top_task+0x1f/0x30
PGD 232a75067 PUD 230947067 PMD 0
Oops: [#1] SMP
CPU: 1 PID: 10994 Comm: a.out Not tainted
Current code use pi_waiters_leftmost to record the leftmost waiter,
but actually it can be get directly from task_struct::pi_waiters
using rb_first(). The performance penalty introduced by rb_first()
should be fine, because normally there aren't that many rtmutexes
chained together for one task.
Current code use pi_waiters_leftmost to record the leftmost waiter,
but actually it can be get directly from task_struct::pi_waiters
using rb_first(). The performance penalty introduced by rb_first()
should be fine, because normally there aren't that many rtmutexes
chained together for one task.
Hi,
Jun Li writes:
>> >> On 6 April 2016 at 15:19, Peter Chen wrote:
>> >> > On Fri, Apr 01, 2016 at 03:21:50PM +0800, Baolin Wang wrote:
>> >> >>
>> >> >> @@ -563,6 +564,8 @@ struct usb_gadget_ops {
>> >> >> struct usb_ep *(*match_ep)(struct
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patch removed the name property from dwapb_port_property.
> The name property is redundant because we can get those info
> from dwapb_gpio dev and pp->idx property.
Where idx is used in such replacements?
> ---
Hi,
Jun Li writes:
>> >> On 6 April 2016 at 15:19, Peter Chen wrote:
>> >> > On Fri, Apr 01, 2016 at 03:21:50PM +0800, Baolin Wang wrote:
>> >> >>
>> >> >> @@ -563,6 +564,8 @@ struct usb_gadget_ops {
>> >> >> struct usb_ep *(*match_ep)(struct usb_gadget *,
>> >> >>
On Wed, Apr 6, 2016 at 10:07 AM, qiujiang wrote:
> This patch removed the name property from dwapb_port_property.
> The name property is redundant because we can get those info
> from dwapb_gpio dev and pp->idx property.
Where idx is used in such replacements?
> --- a/drivers/gpio/gpio-dwapb.c
Colin King wrote:
> From: Colin Ian King
>
> The OID_sha224 case is missing a break and it falls through
> to the -ENOPKG error default. Since HASH_ALGO_SHA224 seems
> to be supported, this looks like an unintentional missing break.
>
>
Colin King wrote:
> From: Colin Ian King
>
> The OID_sha224 case is missing a break and it falls through
> to the -ENOPKG error default. Since HASH_ALGO_SHA224 seems
> to be supported, this looks like an unintentional missing break.
>
> Fixes: 07f081fb5057 ("PKCS#7: Add OIDs for sha224,
On Tue, Apr 05, 2016 at 11:14:54PM -0400, Vivien Didelot wrote:
> Hi Andrew,
>
> Andrew Lunn writes:
>
> >>mutex_lock(>smi_mutex);
> >> - ret = _mv88e6xxx_port_fdb_load(ds, port, fdb->addr, fdb->vid, state);
> >> + if (_mv88e6xxx_port_fdb_load(ds, port, fdb->addr,
On Tue, Apr 05, 2016 at 11:14:54PM -0400, Vivien Didelot wrote:
> Hi Andrew,
>
> Andrew Lunn writes:
>
> >>mutex_lock(>smi_mutex);
> >> - ret = _mv88e6xxx_port_fdb_load(ds, port, fdb->addr, fdb->vid, state);
> >> + if (_mv88e6xxx_port_fdb_load(ds, port, fdb->addr, fdb->vid, state))
> >> +
clk_get on a disabled clock node will return EPROBE_DEFER, which can
cause drivers to be deferred forever if such clocks are referenced in
their clocks property.
Update the various disabled external clock nodes to default to a
frequency of 0, but don't disable them to prevent this.
Hi,
On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote:
> Hi,
>
>
> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote:
>>> Adding vendor specific directories in phy to group
>>> phy drivers under
clk_get on a disabled clock node will return EPROBE_DEFER, which can
cause drivers to be deferred forever if such clocks are referenced in
their clocks property.
Update the various disabled external clock nodes to default to a
frequency of 0, but don't disable them to prevent this.
Hi,
On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote:
> Hi,
>
>
> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote:
>>> Adding vendor specific directories in phy to group
>>> phy drivers under their respective
> -Original Message-
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Wednesday, April 06, 2016 8:22 PM
> To: Jun Li ; Baolin Wang ; Peter
> Chen
> Cc: Greg KH ; Sebastian Reichel
>
> -Original Message-
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Wednesday, April 06, 2016 8:22 PM
> To: Jun Li ; Baolin Wang ; Peter
> Chen
> Cc: Greg KH ; Sebastian Reichel
> ; Dmitry Eremin-Solenikov ; David
> Woodhouse ; Peter Chen ;
> Alan Stern ; r.bald...@samsung.com;
Hi,
On Wednesday 06 April 2016 05:55 AM, Yoshihiro Shimoda wrote:
> Hi,
>
>> From: Kishon Vijay Abraham I
>> Sent: Tuesday, April 05, 2016 7:54 PM
>>
>> Hi,
>>
>> On Thursday 03 March 2016 03:39 PM, Yoshihiro Shimoda wrote:
>>> To handle the VBUS on/off by a regulator driver, this patch adds
>>>
Hi,
On Wednesday 06 April 2016 05:55 AM, Yoshihiro Shimoda wrote:
> Hi,
>
>> From: Kishon Vijay Abraham I
>> Sent: Tuesday, April 05, 2016 7:54 PM
>>
>> Hi,
>>
>> On Thursday 03 March 2016 03:39 PM, Yoshihiro Shimoda wrote:
>>> To handle the VBUS on/off by a regulator driver, this patch adds
>>>
This patchset fixes three issues found with perf probe on ppc64le:
1. 'perf test kallsyms' failure on ppc64le (reported by Michael
Ellerman). This was due to the symbols being fixed up during symbol
table load. This is fixed in patch 2 by delaying symbol fixup until
later.
2. perf probe function
This patchset fixes three issues found with perf probe on ppc64le:
1. 'perf test kallsyms' failure on ppc64le (reported by Michael
Ellerman). This was due to the symbols being fixed up during symbol
table load. This is fixed in patch 2 by delaying symbol fixup until
later.
2. perf probe function
Hi,
On Friday 04 March 2016 09:49 PM, Thierry Reding wrote:
> From: Thierry Reding
>
> Add a new driver for the XUSB pad controller found on NVIDIA Tegra SoCs.
> This hardware block used to be exposed as a pin controller, but it turns
> out that this isn't a good fit. The
Hi,
On Friday 04 March 2016 09:49 PM, Thierry Reding wrote:
> From: Thierry Reding
>
> Add a new driver for the XUSB pad controller found on NVIDIA Tegra SoCs.
> This hardware block used to be exposed as a pin controller, but it turns
> out that this isn't a good fit. The new driver and DT
From: Abdelmajid MLAYEH
This will be printed anyways by neigh_suspect
Signed-off-by: Abdelmajid Mlayeh
---
net/core/neighbour.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index
From: Abdelmajid MLAYEH
This will be printed anyways by neigh_suspect
Signed-off-by: Abdelmajid Mlayeh
---
net/core/neighbour.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index f18ae91..bf20118 100644
--- a/net/core/neighbour.c
+++
On 04/04/16 18:27, Ludovic Desroches wrote:
> In order to remove the SDHCI_QUIRK2_NEED_DELAY_AFTER_INT_CLK_RST and to
> reduce code duplication, put the code relative to the SD clock
> configuration in a function which can be used by hosts for the
> implementation of the set_clock() callback.
>
>
On 04/04/16 18:27, Ludovic Desroches wrote:
> In order to remove the SDHCI_QUIRK2_NEED_DELAY_AFTER_INT_CLK_RST and to
> reduce code duplication, put the code relative to the SD clock
> configuration in a function which can be used by hosts for the
> implementation of the set_clock() callback.
>
>
On Tue 05-04-16 20:12:51, Tetsuo Handa wrote:
[...]
> What I can observe under OOM livelock condition is a three-way dependency
> loop.
>
> (1) An OOM victim (which has TIF_MEMDIE) is unable to make forward progress
> due to blocked at unkillable lock waiting for other thread's memory
>
On Tue 05-04-16 20:12:51, Tetsuo Handa wrote:
[...]
> What I can observe under OOM livelock condition is a three-way dependency
> loop.
>
> (1) An OOM victim (which has TIF_MEMDIE) is unable to make forward progress
> due to blocked at unkillable lock waiting for other thread's memory
>
Hello.
On 4/6/2016 9:44 AM, Lu Baolu wrote:
+struct intel_mux_dev {
+ struct device *dev;
+ char*extcon_name;
+ char*cable_name;
+ int (*cable_set_cb)(struct intel_mux_dev *mux);
+ int (*cable_unset_cb)(struct
Hello.
On 4/6/2016 9:44 AM, Lu Baolu wrote:
+struct intel_mux_dev {
+ struct device *dev;
+ char*extcon_name;
+ char*cable_name;
+ int (*cable_set_cb)(struct intel_mux_dev *mux);
+ int (*cable_unset_cb)(struct
2016-04-06 10:21+0800, rhett rhett:
> 8499907b52c9cebf3c1a4aaa63b84bd9c3c1ff3d
> arch/x86/kvm/hyperv.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
> index 01bd7b7..e831032 100644
> --- a/arch/x86/kvm/hyperv.c
> +++ b/arch/x86/kvm/hyperv.c
2016-04-06 10:21+0800, rhett rhett:
> 8499907b52c9cebf3c1a4aaa63b84bd9c3c1ff3d
> arch/x86/kvm/hyperv.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
> index 01bd7b7..e831032 100644
> --- a/arch/x86/kvm/hyperv.c
> +++ b/arch/x86/kvm/hyperv.c
2016-04-06 10:40+0700, Suravee Suthikulpanit:
> On 04/05/2016 09:56 PM, Radim Krčmář wrote:
>>I meant to change the place where we remember that is_running must not
>>be true. Something like
>>
>> svm_vcpu_blocking(struct kvm_vcpu *vcpu):
>> vcpu->is_blocking = true;
>>
2016-04-06 10:40+0700, Suravee Suthikulpanit:
> On 04/05/2016 09:56 PM, Radim Krčmář wrote:
>>I meant to change the place where we remember that is_running must not
>>be true. Something like
>>
>> svm_vcpu_blocking(struct kvm_vcpu *vcpu):
>> vcpu->is_blocking = true;
>>
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
Move xen_early_init() before efi_init(), then when calling efi_init()
could initialize Xen specific UEFI.
Check if it runs on Xen hypervisor through the flat dts.
Cc: Russell King
Signed-off-by: Shannon Zhao
So far, we used to treat probe point offsets as being offset from the
LEP. However, userspace applications (objdump/readelf) always show
disassembly and offsets from the function GEP. This is confusing to the
user as we will end up probing at an address different from what the
user expects when
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
Move xen_early_init() before efi_init(), then when calling efi_init()
could initialize Xen specific UEFI.
Check if it runs on Xen hypervisor through the flat dts.
Cc: Russell King
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano
So far, we used to treat probe point offsets as being offset from the
LEP. However, userspace applications (objdump/readelf) always show
disassembly and offsets from the function GEP. This is confusing to the
user as we will end up probing at an address different from what the
user expects when
ppc64le functions have a Global Entry Point (GEP) and a Local Entry
Point (LEP). While placing a probe, we always prefer the LEP since it
catches function calls through both the GEP and the LEP. In order to do
this, we fixup the function entry points during elf symbol table lookup
to point to the
ppc64le functions have a Global Entry Point (GEP) and a Local Entry
Point (LEP). While placing a probe, we always prefer the LEP since it
catches function calls through both the GEP and the LEP. In order to do
this, we fixup the function entry points during elf symbol table lookup
to point to the
On Tue, Apr 05, 2016 at 05:29:17PM +0100, Nicholas Sim wrote:
> Added braces on if arm of if statement where else arm already needs braces
> as suggested for clarity in Documentation/CodingStyle
>
> Signed-off-by: Nicholas Sim
> ---
> drivers/staging/rts5208/ms.c | 3
On Tue, Apr 05, 2016 at 05:29:17PM +0100, Nicholas Sim wrote:
> Added braces on if arm of if statement where else arm already needs braces
> as suggested for clarity in Documentation/CodingStyle
>
> Signed-off-by: Nicholas Sim
> ---
> drivers/staging/rts5208/ms.c | 3 ++-
> 1 file changed, 2
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
The kernel will get the event-channel IRQ through
HVM_PARAM_CALLBACK_IRQ.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Reviewed-by: Julien Grall
On Wed, Apr 06, 2016 at 15:12:43, Pali Rohár wrote:
> > > > For other TI wilink chips there are -ap.bin firmware files
> > > > (wl1271-fw-ap.bin and wl128x-fw-ap.bin) which support AP mode.
> > > > But for
> > > > wl1251 firmware file with guessed name "wl1251-fw-ap.bin" is
> > > > missing.
> >
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
The kernel will get the event-channel IRQ through
HVM_PARAM_CALLBACK_IRQ.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Reviewed-by: Julien Grall
Regards,
--
Julien Grall
On Wed, Apr 06, 2016 at 15:12:43, Pali Rohár wrote:
> > > > For other TI wilink chips there are -ap.bin firmware files
> > > > (wl1271-fw-ap.bin and wl128x-fw-ap.bin) which support AP mode.
> > > > But for
> > > > wl1251 firmware file with guessed name "wl1251-fw-ap.bin" is
> > > > missing.
> >
Hi Geert,
On Wed, Apr 06, 2016 at 08:51:50AM +0200, Geert Uytterhoeven wrote:
> Hi Yuri,
>
> On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov wrote:
> > This version is rebased on kernel v4.6-rc2, and has fixes in signal
> > subsystem.
> > It works with updated glibc [1]
On Tue, Apr 05, 2016 at 03:26:11PM +0200, Anna-Maria Gleixner wrote:
> On Mon, 4 Apr 2016, Ralf Baechle wrote:
>
> > On Mon, Apr 04, 2016 at 02:18:03PM +0200, Anna-Maria Gleixner wrote:
> >
> > > Since commit 1cf4f629d9d2 ("cpu/hotplug: Move online calls to
> > > hotplugged cpu") it is ensured
Hi,
(please make sure to break your lines at
80-characters. Documentation/email-clients.txt has several tips for
different email clients ;-))
"Du, Changbin" writes:
>> > @@ -648,6 +687,12 @@ int dwc3_debugfs_init(struct dwc3 *dwc)
>> >goto err1;
>> >}
>>
Hi Geert,
On Wed, Apr 06, 2016 at 08:51:50AM +0200, Geert Uytterhoeven wrote:
> Hi Yuri,
>
> On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov wrote:
> > This version is rebased on kernel v4.6-rc2, and has fixes in signal
> > subsystem.
> > It works with updated glibc [1] (though very draft), and
On Tue, Apr 05, 2016 at 03:26:11PM +0200, Anna-Maria Gleixner wrote:
> On Mon, 4 Apr 2016, Ralf Baechle wrote:
>
> > On Mon, Apr 04, 2016 at 02:18:03PM +0200, Anna-Maria Gleixner wrote:
> >
> > > Since commit 1cf4f629d9d2 ("cpu/hotplug: Move online calls to
> > > hotplugged cpu") it is ensured
Hi,
(please make sure to break your lines at
80-characters. Documentation/email-clients.txt has several tips for
different email clients ;-))
"Du, Changbin" writes:
>> > @@ -648,6 +687,12 @@ int dwc3_debugfs_init(struct dwc3 *dwc)
>> >goto err1;
>> >}
>> >
>> > + file =
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
This new delivery type which is for ARM shares the same value with
HVM_PARAM_CALLBACK_TYPE_VECTOR which is for x86.
val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 8 stands the interrupt mode is edge(1) or level(0) and
bit 9 stands
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
This new delivery type which is for ARM shares the same value with
HVM_PARAM_CALLBACK_TYPE_VECTOR which is for x86.
val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 8 stands the interrupt mode is edge(1) or level(0) and
bit 9 stands
Hi,
Jun Li writes:
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Baolin Wang
>> Sent: Wednesday, April 06, 2016 6:47 PM
>> To: Peter Chen
>> Cc: Felipe Balbi
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
Add a bus_notifier for AMBA bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Hi,
Jun Li writes:
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Baolin Wang
>> Sent: Wednesday, April 06, 2016 6:47 PM
>> To: Peter Chen
>> Cc: Felipe Balbi ; Greg KH ;
>> Sebastian Reichel ; Dmitry
Hi Shannon,
On 01/04/2016 16:49, Shannon Zhao wrote:
Add a bus_notifier for AMBA bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Reviewed-by: Julien Grall
Regards,
--
Julien Grall
On 2016/03/31 at 11:52, Xunlei Pang wrote:
> Hi Bao,
>
> On 2016/03/31 at 10:52, Baoquan He wrote:
>> On 03/31/16 at 10:43am, Minfei Huang wrote:
>>> On 03/30/16 at 08:30pm, Baoquan He wrote:
Hi Xunlei,
I have two questions.
One is do we still need Minfei's patch if this
On 2016/03/31 at 11:52, Xunlei Pang wrote:
> Hi Bao,
>
> On 2016/03/31 at 10:52, Baoquan He wrote:
>> On 03/31/16 at 10:43am, Minfei Huang wrote:
>>> On 03/30/16 at 08:30pm, Baoquan He wrote:
Hi Xunlei,
I have two questions.
One is do we still need Minfei's patch if this
Remove dead #if blocks referencing previously removed Kconfig options.
Signed-off-by: Valentin Rothberg
---
arch/blackfin/mach-bf537/boards/stamp.c | 22 --
1 file changed, 22 deletions(-)
diff --git a/arch/blackfin/mach-bf537/boards/stamp.c
Remove dead #if blocks referencing previously removed Kconfig options.
Signed-off-by: Valentin Rothberg
---
arch/blackfin/mach-bf537/boards/stamp.c | 22 --
1 file changed, 22 deletions(-)
diff --git a/arch/blackfin/mach-bf537/boards/stamp.c
Hi
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Baolin Wang
> Sent: Wednesday, April 06, 2016 6:47 PM
> To: Peter Chen
> Cc: Felipe Balbi ; Greg KH
Hi
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Baolin Wang
> Sent: Wednesday, April 06, 2016 6:47 PM
> To: Peter Chen
> Cc: Felipe Balbi ; Greg KH ;
> Sebastian Reichel ; Dmitry Eremin-Solenikov
> ; David Woodhouse
Hi Shannon,
Sorry to come late in the review process.
On 01/04/2016 16:49, Shannon Zhao wrote:
Add a bus_notifier for platform bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
Hi Shannon,
Sorry to come late in the review process.
On 01/04/2016 16:49, Shannon Zhao wrote:
Add a bus_notifier for platform bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
drivers/xen/Makefile
From: Kelvin Cheung
- Rename the file to loongson1-cpufreq.c
- Use kcalloc() instead of kzalloc()
- Use devm_kzalloc() instead of global structure
- Use dev_get_platdata() to access the platform_data field
instead of referencing it directly
- Remove superfluous error
On Wednesday 06 April 2016 13:30:22 Machani, Yaniv wrote:
> On Mon, Apr 04, 2016 at 15:39:44, Pali Rohár wrote:
> > > In linux-firmware repository [1] is missing AP firmware for TI
> > > wl1251 chip. There is only STA firmware wl1251-fw.bin which
> > > supports managed and ad-hoc modes.
> > >
> >
On 6 April 2016 at 10:37, Morten Rasmussen wrote:
> On Tue, Apr 05, 2016 at 06:00:40PM +0100, Dietmar Eggemann wrote:
>> @@ -2893,8 +2906,12 @@ static void attach_entity_load_avg(struct cfs_rq
>> *cfs_rq, struct sched_entity *s
>> se->avg.last_update_time =
From: Kelvin Cheung
- Rename the file to loongson1-cpufreq.c
- Use kcalloc() instead of kzalloc()
- Use devm_kzalloc() instead of global structure
- Use dev_get_platdata() to access the platform_data field
instead of referencing it directly
- Remove superfluous error messages
Signed-off-by:
On Wednesday 06 April 2016 13:30:22 Machani, Yaniv wrote:
> On Mon, Apr 04, 2016 at 15:39:44, Pali Rohár wrote:
> > > In linux-firmware repository [1] is missing AP firmware for TI
> > > wl1251 chip. There is only STA firmware wl1251-fw.bin which
> > > supports managed and ad-hoc modes.
> > >
> >
On 6 April 2016 at 10:37, Morten Rasmussen wrote:
> On Tue, Apr 05, 2016 at 06:00:40PM +0100, Dietmar Eggemann wrote:
>> @@ -2893,8 +2906,12 @@ static void attach_entity_load_avg(struct cfs_rq
>> *cfs_rq, struct sched_entity *s
>> se->avg.last_update_time = cfs_rq->avg.last_update_time;
From: Kelvin Cheung
This patch adds GPIO driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
drivers/gpio/Kconfig | 7 +++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-loongson1.c | 102
From: Kelvin Cheung
This patch adds GPIO driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
drivers/gpio/Kconfig | 7 +++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-loongson1.c | 102 ++
3 files changed, 110 insertions(+)
From: Kelvin Cheung
- Rename the file to clk-loongson1.c
- Add AC97, DMA and NAND clock
- Update clock names
- Remove superfluous error messages
Signed-off-by: Kelvin Cheung
---
drivers/clk/Makefile| 2 +-
drivers/clk/clk-loongson1.c
From: Kelvin Cheung
- Add DMA device
- Add NAND device
- Add GPIO device
- Add LED device
- Update the defconfig and rename it to loongson1b_defconfig
- Fix ioremap size
- Other minor fixes
Signed-off-by: Kelvin Cheung
---
arch/mips/Kconfig
From: Kelvin Cheung
This patch adds DMA Engine driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
drivers/dma/Kconfig | 9 +
drivers/dma/Makefile| 1 +
drivers/dma/loongson1-dma.c | 546
From: Kelvin Cheung
This patchset is to add NAND, DMA and GPIO support for Loongson1B,
and moreover, include some updates/fixes.
This applies on top of mips-for-linux-next.
Thanks!
Kelvin Cheung (7):
clk: Loongson1: Update clocks of Loongson1B
cpufreq: Loongson1:
From: Kelvin Cheung
- Rename the file to clk-loongson1.c
- Add AC97, DMA and NAND clock
- Update clock names
- Remove superfluous error messages
Signed-off-by: Kelvin Cheung
---
drivers/clk/Makefile| 2 +-
drivers/clk/clk-loongson1.c | 163
From: Kelvin Cheung
- Add DMA device
- Add NAND device
- Add GPIO device
- Add LED device
- Update the defconfig and rename it to loongson1b_defconfig
- Fix ioremap size
- Other minor fixes
Signed-off-by: Kelvin Cheung
---
arch/mips/Kconfig | 2 +
From: Kelvin Cheung
This patch adds DMA Engine driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
drivers/dma/Kconfig | 9 +
drivers/dma/Makefile| 1 +
drivers/dma/loongson1-dma.c | 546
3 files changed, 556 insertions(+)
From: Kelvin Cheung
This patchset is to add NAND, DMA and GPIO support for Loongson1B,
and moreover, include some updates/fixes.
This applies on top of mips-for-linux-next.
Thanks!
Kelvin Cheung (7):
clk: Loongson1: Update clocks of Loongson1B
cpufreq: Loongson1: Update cpufreq of
Cc Chanho Min, Kyungsik Lee
Hello,
On (04/06/16 10:39), Rui Salvaterra wrote:
> > may we please ask you to test the patch first? quite possible there
> > is nothing to fix there; I've no access to mips h/w but the patch
> > seems correct to me.
> >
> > LZ4_READ_LITTLEENDIAN_16 does
Cc Chanho Min, Kyungsik Lee
Hello,
On (04/06/16 10:39), Rui Salvaterra wrote:
> > may we please ask you to test the patch first? quite possible there
> > is nothing to fix there; I've no access to mips h/w but the patch
> > seems correct to me.
> >
> > LZ4_READ_LITTLEENDIAN_16 does
1201 - 1300 of 1854 matches
Mail list logo