Function klsi_105_open() calls usb_control_msg() and checks its return
value. When the return value is unexpected, it only assigns the error
code to the return variable retval, but does not terminate the exception
path. This patch fixes the bug by inserting "goto exit;" when the call
to usb_control
This patch introduces the RX checksum function to check the
status of the hardware calculated checksum and its error and
appropriately convey status to the upper stack in skb->ip_summed
field.
We only support checksum for IPv4, UDP(over IPv4 or IPv6),
TCP(over IPv4 or IPv6) and SCTP but we support
> From: Philippe Reynes [mailto:trem...@gmail.com]
> Sent: Monday, November 28, 2016 2:52 PM
>
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> Signed-off-by: Philippe Reynes
Acked-by: Rasesh Mody
> ---
> drivers/net/ethernet
When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the
boot cpu can be replaced. During the hot add event, the message
NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
is output implying that the NMI watchdog was disabled at some point. This
is not t
Hi Peter,
On Tue, Nov 29, 2016 at 10:23:14AM +0100, Daniel Vetter wrote:
> We already had a super-short blurb, but worth extending it I think:
> We're still pretty far away from anything like a consensus, but
> there's clearly a lot of people who prefer an as-light as possible
> approach to conver
On Mon, Nov 28, 2016 at 08:08:57PM -0800, Linus Torvalds wrote:
> On Mon, Nov 28, 2016 at 5:15 PM, Ben Hutchings wrote:
> >>
> >> The modversions stuff may just be too painful to bother with. Very few
> >> people probably use it, and the ones that do likely don't have any
> >> overriding reason wh
On Mon, Nov 21, 2016 at 05:06:54PM +0100, Borislav Petkov wrote:
> IOW, what's the worst thing that can happen if we did this below?
>
> We basically get rid of the detection and switch the timer to broadcast
> mode immediately on the halting CPU.
>
> amd_e400_idle() is behind an "if (cpu_has_bug
* Josh Poimboeuf wrote:
> Hi tip-bot,
>
> On Mon, Nov 28, 2016 at 11:13:15PM -0800, tip-bot for Josh Poimboeuf wrote:
> > Commit-ID: 8e8d8725d46d93ceffd3e708d905bc101a1905b5
> > Gitweb:
> > http://git.kernel.org/tip/8e8d8725d46d93ceffd3e708d905bc101a1905b5
> > Author: Josh Poimboeuf
On Tue, Nov 29, 2016 at 02:59:58PM +0200, Heikki Krogerus wrote:
> Hi Guenter,
>
> On Mon, Nov 28, 2016 at 12:11:43PM -0800, Guenter Roeck wrote:
> > Personally I don't really care about a module parameter; as mentioned above,
> > I would expect the preference, if it needs to be selectable, to be
On Tue, Nov 29, 2016 at 1:29 PM, Peter Zijlstra wrote:
> On Tue, Nov 29, 2016 at 12:52:04PM +0100, Geert Uytterhoeven wrote:
>> > Nah, users don't need more senseless options. This is really only useful
>> > for dinky platforms or platforms with limited static image size (like
>> > sparc64).
>> >
* Adam Borowski wrote:
> Here's some history:
> The day of -rc1, multiple people immediately reported the breakage; it was
> quickly found out that reverting 784d5699eddc fixes it. A "going forward"
> patch has been posted but was insufficient; when the real devs went to bed
> the last message
On Tue, Nov 29, 2016 at 02:26:47PM +0100, Geert Uytterhoeven wrote:
> On Tue, Nov 29, 2016 at 1:29 PM, Peter Zijlstra wrote:
> > On Tue, Nov 29, 2016 at 12:52:04PM +0100, Geert Uytterhoeven wrote:
> >> Not because of platforms with not limited memory, but because of platforms
> >> with boot loade
Hi Peter,
On Tue, Nov 29, 2016 at 2:31 PM, Peter Zijlstra wrote:
> On Tue, Nov 29, 2016 at 02:26:47PM +0100, Geert Uytterhoeven wrote:
>> On Tue, Nov 29, 2016 at 1:29 PM, Peter Zijlstra wrote:
>> > On Tue, Nov 29, 2016 at 12:52:04PM +0100, Geert Uytterhoeven wrote:
>
>> >> Not because of platfor
From: Hanjun Guo
Adding ACPI support for platform MSI, we need to retrieve the
dev id in ACPI way instead of device tree, we already have
a well formed function its_pmsi_prepare() to get the dev id
but it's OF dependent, so collect OF related code and put them
into a single function to make its_p
From: Hanjun Guo
For devices connecting to ITS, it needs dev id to identify
itself, and this dev id is represented in the IORT table in
named componant node [1] for platform devices, so in this
patch we will scan the IORT to retrieve device's dev id.
Introduce iort_pmsi_get_dev_id() with pointer
From: Hanjun Guo
With the introduction of its_pmsi_init_one(), we can add some code
on top for ACPI support of platform MSI.
We are scanning the MADT table to get the ITS entry(ies), then use
the information to create the platform msi domain for devices connect
to it, just like the PCI MSI for I
From: Hanjun Guo
We are missing req_id's comment for iort_dev_find_its_id(),
add it back.
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
Cc: Tomasz Nowicki
---
drivers/acpi/arm64/iort.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
From: Hanjun Guo
Cleanup iort_match_node_callback() a little bit to reduce
some lines of code, aslo fix the indentation in iort_scan_node().
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
Cc: Marc Zyngier
Cc: Tomasz Nowicki
---
drivers/acpi/arm64/iort.c | 10 +++---
1 file changed, 3 i
From: Hanjun Guo
Introduce its_pmsi_init_one() to refactor the code to isolate
ACPI&DT common code to prepare for ACPI later.
Signed-off-by: Hanjun Guo
Tested-by: Sinan Kaya
Cc: Marc Zyngier
Cc: Tomasz Nowicki
Cc: Thomas Gleixner
---
drivers/irqchip/irq-gic-v3-its-platform-msi.c | 45 +
From: Hanjun Guo
The head file is strictly in alphabetic order now, so let's
be the rule breaker. As acpi_iort.h includes acpi.h so remove
the duplidate acpi.h inclusion as well.
Signed-off-by: Hanjun Guo
Cc: Marc Zyngier
Cc: Tomasz Nowicki
---
drivers/irqchip/irq-gic-v3-its.c | 3 +--
1 fil
From: Hanjun Guo
iort_node_get_id() has two output, one is the mapped ids,
the other is the referenced parent node which is returned
from the function.
For now we need a API just return its parent node for
single mapping, so just update this function slightly then
reuse it later.
Signed-off-by:
Hi Peter,
On 29 November 2016 at 12:46, Peter Zijlstra wrote:
> On Tue, Nov 29, 2016 at 08:43:33AM +0100, Michael Kerrisk (man-pages) wrote:
>> >
>> > In any case, for the case of autogroup, the behaviour has always been,
>> > autogroups came quite late.
>>
>> This ("the behavior has always been"
On Tue, 29 Nov 2016, Alexander Kochetkov wrote:
> After a cpufreq transition, update the clockevent's frequency
> by fetching the new clock rate from the clock framework and
> reprogram the next clock event.
The frequency change would not only affect the clockevent device, it also
would affect th
Hello,
This patch series contain:
- devicetree bindings clarification for rockchip timers
- dts files fixes for rk3228-evb, rk3229-evb and rk3188
- implementation of clocksource for rockchip SoC
The clock supplying the arm-global-timer on the rk3188 is coming from the
the cpu clock itself and thu
Make all properties description in form '"rockchip,-timer",
"rockchip,rk3288-timer"' for all chips found in linux kernel.
Suggested-by: Heiko Stübner
Signed-off-by: Alexander Kochetkov
---
.../bindings/timer/rockchip,rk-timer.txt | 12 +---
1 file changed, 9 insertions(+), 3
Property set to '"rockchip,rk3229-timer", "rockchip,rk3288-timer"'
to match devicetree bindings.
Signed-off-by: Alexander Kochetkov
---
arch/arm/boot/dts/rk3229-evb.dts |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/rk3229-evb.dts b/arch/arm/boot/dts/rk3229-evb.dts
From: Hanjun Guo
With the platform msi domain created for ITS, irqchip such as
mbi-gen connecting ITS, which needs ctreate its own irqdomain.
Fortunately with the platform msi support upstreamed by Marc,
we just need to add minor code to make it run properly.
platform_msi_create_device_domain()
Use of functions has been ceased by previous commit.
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/clocksource/rockchip_timer.c
b/drivers/clocksource/rockchip_timer.c
index aa9ccd1..a17dc61 10
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/clocksource/rockchip_timer.c
b/drivers/clocksource/rockchip_timer.c
index c2b0454..6224aa9 100644
--- a/drivers/clocksource/rockchip_ti
This allow to enable timer without enabling interrupts from it.
As that mode will be used in clocksource implementation.
This is refactoring step without functional changes.
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c |8
1 file changed, 4 insertions
From: Hanjun Guo
iort_node_get_id() for now only support NC(named componant)->SMMU
or NC->ITS cases, we also have other device topology such NC->
SMMU->ITS, so rework iort_node_get_id() for those cases.
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
---
drivers/acpi/arm64/iort.c | 59 +++
From: Hanjun Guo
v3 -> v4:
- Drop mbi-gen patches to just submit platform msi support because
will rebase mbi-gen patches on top of Agustin's patchset, and
discusion
is going there.
- Add a patch to support device topology such as NC(named componant,
paltform
Currently rockchip_timer can be used as a scheduler clock. We properly
marked rk_timer_sched_clock_read() as notrace but we then call another
function rk_timer_counter_read() that _wasn't_ notrace.
Having a traceable function in the sched_clock() path leads to a recursion
within ftrace and a kerne
On Tue, 2016-11-29 at 10:10 +0100, Michael Kerrisk (man-pages) wrote:
> Let's try and go further. How's this:
>
>When scheduling non-real-time processes (i.e., those scheduled
>under the SCHED_OTHER, SCHED_BATCH, and SCHED_IDLE policies), the
>CFS scheduler employs a t
The clock supplying the arm-global-timer on the rk3188 is coming from the
the cpu clock itself and thus changes its rate everytime cpufreq adjusts
the cpu frequency making this timer unsuitable as a stable clocksource.
The rk3188, rk3288 and following socs share a separate timer block already
hand
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/clocksource/rockchip_timer.c
b/drivers/clocksource/rockchip_timer.c
index 61c3bb1..c2b0454 100644
--- a/drivers/clocksource/rockchi
The patch add two timers to all rk3188 based boards.
The first timer is from alive subsystem and it act as a backup
for the local timers at sleep time. It act the same as timers
on other rockchip chips already present in kernel.
The second timer is from CPU subsystem and act as replacement
for th
Property set to '"rockchip,rk3228-timer", "rockchip,rk3288-timer"'
to match devicetree bindings.
Signed-off-by: Alexander Kochetkov
---
arch/arm/boot/dts/rk3228-evb.dts |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/rk3228-evb.dts b/arch/arm/boot/dts/rk3228-evb.dts
From: Hanjun Guo
With the platform msi domain created, we can set up the msi domain
for a platform device when it's probed.
In order to do that, we need to get the domain that the platform
device connecting to, so the iort_get_platform_device_domain() is
introduced to retrieve the domain from io
Pass rk_timer instead of clock_event_device to low lever timer routines.
So that code could be reused by clocksource implementation.
This is refactoring step without functional changes.
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c | 47 +++---
On Tue, Nov 29, 2016 at 02:39:20PM +0100, Geert Uytterhoeven wrote:
> > Not understanding, why would a user ever need it? The platform knows if
> > its has funny boot image size limits, no?
>
> The boot loader does not come with the kernel, so the platform cannot
> know for sure.
Why would anybo
arm-global-timer can provide clockevents, clocksource and shed_clock. But
on rk3188 platform it provide only clocksource and shed_clock. clockevents
from arm-global-timer is not used by kernel because there is another
clockevent provider with higher rating (smp-twd).
My commit from the series imp
The patch move ce field out of struct bc_timer into struct
rk_clock_event_device and rename struct bc_timer to struct rk_timer.
This is refactoring step without functional changes.
Signed-off-by: Alexander Kochetkov
---
drivers/clocksource/rockchip_timer.c | 33 ++-
Commit 4efca4ed ("kbuild: modversions for EXPORT_SYMBOL() for asm") adds
modversion support for symbols exported from asm files. Architectures
must include C-style declarations for those symbols in asm/asm-prototypes.h
in order for them to be versioned.
Add these declarations for x86, and an archi
Add MEI Lewisburg PCH IDs for Purley based workstations.
Cc: # 4.8.x
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hw-me-regs.h | 2 ++
drivers/misc/mei/pci-me.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/misc/mei/hw-me-regs.h b/drive
On Tue, 2016-11-29 at 14:20 +0100, Greg KH wrote:
> On Tue, Nov 29, 2016 at 02:59:58PM +0200, Heikki Krogerus wrote:
> > Hi Guenter,
> >
> > On Mon, Nov 28, 2016 at 12:11:43PM -0800, Guenter Roeck wrote:
> > > Personally I don't really care about a module parameter; as mentioned
> > > above,
> >
On Tue 2016-10-18 19:08:31, Peter Zijlstra wrote:
> Some people figured vprintk_emit() makes for a nice API and exported
> it, bypassing the kdb trap.
I think that nobody saw this problem because kdb_trap_printk was
used only for a limited number of printk's. It is just a trick
how to use generic
Add pin configuration support for Gyro-ADC, named ADI on r8a7791 SoC.
The Gyro-ADC supports three different configurations:
a single ADC (adi and adi_b groups), 2 ADCs selectable through a single
channel select signal (adi_chsel1 and adi_chsel1_b groups), up to 4 ADCs
through 2 channel select sign
On Tue, 29 Nov 2016, Borislav Petkov wrote:
> On Mon, Nov 21, 2016 at 05:06:54PM +0100, Borislav Petkov wrote:
> > IOW, what's the worst thing that can happen if we did this below?
> >
> > We basically get rid of the detection and switch the timer to broadcast
> > mode immediately on the halting C
On Tue, Nov 29, 2016 at 02:48:46PM +0100, Oliver Neukum wrote:
> On Tue, 2016-11-29 at 14:20 +0100, Greg KH wrote:
> > On Tue, Nov 29, 2016 at 02:59:58PM +0200, Heikki Krogerus wrote:
> > > Hi Guenter,
> > >
> > > On Mon, Nov 28, 2016 at 12:11:43PM -0800, Guenter Roeck wrote:
> > > > Personally I
On Tue 2016-10-18 19:08:32, Peter Zijlstra wrote:
> Add add the 'force_early_printk' kernel parameter to override printk()
> and force it into early_printk(). This bypasses all the cruft and fail
> from printk() and makes things work again.
IMHO, the patch makes perfect sense and helps with debugg
On Tue, Nov 22, 2016 at 01:49:22PM +, csmanjuvi...@gmail.com wrote:
> From: Manjunath Goudar
>
> Use the module_platform_driver macro to do module init/exit.
> This eliminates a lot of boilerplate.This also removes
> checkpatch.pl errors.
>
> Signed-off-by: Manjunath Goudar
> Cc: Arnd Bergm
How about the attached? Obviously it need extending to other drivers.
I thought that if I'm changing the module_param annotations anyway then it's
probably worth bunging in an extra parameter that notes what the parameter
modifies (ioport, iomem, etc.) for future reference, even if we don't store
On Tue, Nov 29, 2016 at 02:16:49PM +0100, Borislav Petkov wrote:
> On Mon, Nov 21, 2016 at 05:06:54PM +0100, Borislav Petkov wrote:
> > IOW, what's the worst thing that can happen if we did this below?
> >
> > We basically get rid of the detection and switch the timer to broadcast
> > mode immedia
Hello Thomas!
> 29 нояб. 2016 г., в 16:42, Thomas Gleixner написал(а):
>
> The frequency change would not only affect the clockevent device, it also
> would affect the clocksource. So the patch is incomplete, but see below.
Looks like kernel disallow change clocksource and shed_clock rate at
run
2016-11-29 03:04-0800, Kui Zhang:
> Looks like my boot issue might be kvm related. System boots fine with
> CONFIG_KVM=m
v4.9-rc6 has some funny changes around modversion, although your bug
looks even more random ...
Can you reproduce with v4.9-rc7 built from a clean repo?
Please send your config
Jamie,
I am really sorry for the huge delay.
On 11/16, Jamie Iles wrote:
>
> Since 00cd5c37af (ptrace: permit ptracing of /sbin/init) we can now
> trace init processes. init is initially protected with
> SIGNAL_UNKILLABLE which will prevent fatal signals such as SIGSTOP, but
> there are a number
On Mon, 28 Nov 2016, Michal Hocko wrote:
> On Sun 27-11-16 00:13:36, Sebastian Andrzej Siewior wrote:
> [...]
> > static void __init init_cpu_node_state(void)
> > {
> > - int cpu;
> > + int node;
> >
> > - for_each_online_cpu(cpu)
> > - node_set_state(cpu_to_node(cpu), N_CPU);
>
On Tue 2016-10-18 19:08:33, Peter Zijlstra wrote:
> In order to avoid multiple CPUs banging on the serial port at the same
> time, add simple serialization. This explicitly deals with nested
> contexts (like IRQs etc.).
>
> Signed-off-by: Peter Zijlstra (Intel)
Makes sense. Just a small comment
On Tue, 29 Nov 2016, Alexander Kochetkov wrote:
> > 29 нояб. 2016 г., в 16:42, Thomas Gleixner написал(а):
> >
> > The frequency change would not only affect the clockevent device, it also
> > would affect the clocksource. So the patch is incomplete, but see below.
> Looks like kernel disallow ch
On 29/11/16 13:42, Thomas Gleixner wrote:
> On Tue, 29 Nov 2016, Alexander Kochetkov wrote:
>
>> After a cpufreq transition, update the clockevent's frequency
>> by fetching the new clock rate from the clock framework and
>> reprogram the next clock event.
>
> The frequency change would not only
Commit-ID: 53938ee427bf27525a63721b7e25d86b8f31f161
Gitweb: http://git.kernel.org/tip/53938ee427bf27525a63721b7e25d86b8f31f161
Author: Josh Poimboeuf
AuthorDate: Mon, 28 Nov 2016 17:06:35 -0600
Committer: Ingo Molnar
CommitDate: Tue, 29 Nov 2016 14:19:50 +0100
scripts/decode_stacktrace
On Tue, Nov 29, 2016 at 10:16:50AM +0100, Peter Zijlstra wrote:
> On Mon, Nov 28, 2016 at 11:52:41PM -0600, Josh Poimboeuf wrote:
> > > We used to do that, but the resulting NMIs were problematic on some
> > > platforms. Perhaps things have gotten better?
> >
> > Did a little digging on git blame
On Tue, Nov 29, 2016 at 11:47:45AM +0100, Neil Armstrong wrote:
> This a repost of the previous RFC at [1] with fixes, the following patches
> will
> be sent via a PULL Request once the Amlogic maintainer acks and takes the DT
> patches to avoid merges conflicts.
>
> The Amlogic Meson SoCs embeds
If kernfs file is empty on a first read, successive read operations
using the same file descriptor will return no data, even when data is
available. Default kernfs 'seq_next' implementation advances iterator
position even when next object is not there. Kernfs 'seq_start' for
following requests will
Dne 28.11.2016 v 07:44 Peter Foley napsal(a):
> Fix reversed conditional checking if HOSTCC is clang.
> Suppress warnings about unsupported optimization options.
> Suppress warnings about unused functions, as they are generated for
> every module and are therefore far too spammy.
> Disable clang's
On Tue, Nov 29, 2016 at 02:29:54PM +0100, Ingo Molnar wrote:
> * Adam Borowski wrote:
>
> > Here's some history:
> > The day of -rc1, multiple people immediately reported the breakage; it was
> > quickly found out that reverting 784d5699eddc fixes it. A "going forward"
> > patch has been posted
Based on the src/dst_port_window_size - if it is set - configure the DMA
channel to use double indexing in order to be able to loop within the
address window.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/omap-dma.c | 63 --
1 file changed, 61 inse
Hi Oleg,
On Tue, Nov 29, 2016 at 03:06:00PM +0100, Oleg Nesterov wrote:
> Jamie,
>
> I am really sorry for the huge delay.
No problem!
> On 11/16, Jamie Iles wrote:
> >
> > Since 00cd5c37af (ptrace: permit ptracing of /sbin/init) we can now
> > trace init processes. init is initially protected
Some slave devices uses address window instead of single register for read
and/or write of data. With the src/dst_port_window_size the address window
can be specified and the DMAengine driver should use this information to
correctly set up the transfer to loop within the provided window.
Signed-of
Hi,
Changes since v2:
- the src/dst_port_window_size is in words, not in bytes (comment updated)
- correct the port_window based configuration in the omap-dma driver
Changes since v1:
- Make sure that the one frame covers the port_window (burst = port_window)
- added comment to explain the double
* Thomas Gleixner wrote:
> On Mon, 21 Nov 2016, Peter Zijlstra wrote:
> > On Mon, Nov 21, 2016 at 09:16:44AM +0100, Thomas Gleixner wrote:
> > > On Sun, 20 Nov 2016, Peter Zijlstra wrote:
> > > > On Sat, Nov 19, 2016 at 01:47:37PM -, Thomas Gleixner wrote:
> > > > > When entering idle, it's
On Fri, 18 Nov 2016, John Stultz wrote:
> From: Liav Rehana
>
> During the calculation of the nsec variable in the inline function
> timekeeping_delta_to_ns, it may undergo a sign extension if its msb
> is set just before the shift. The sign extension may, in some cases,
> gain it a value near th
On Mon, Nov 28, 2016 at 05:40:46PM -0200, Arnaldo Carvalho de Melo wrote:
SNIP
> CC /tmp/build/perf/builtin-buildid-list.o
> LD /tmp/build/perf/pmu-events/pmu-events-in.o
> CC /tmp/build/perf/arch/x86/util/intel-bts.o
> CC /tmp/build/perf/builtin-buildid-cache.o
>
Originally pfn_pte(pfn, prot) macro is implemented incorrectly
and truncates the most significant byte in the value of PTE
(Page Table Entry). It leads to the creation of invalid page
mapping in the kernel with PAE40 if the physical page frame
resides in the memory above of 4GB boundary.
The behav
Hi Darren,
On 11/29/2016 03:40 AM, Jan Kara wrote:
> Hello,
>
> Thanks for report. I suspect this bug got lost in the noise of
> linux-kernel. Adding more relevant lists and people to CC.
>
> Honza
>
> On Thu 20-10-16 15:24:37, Darre
Em Tue, Nov 29, 2016 at 03:28:08PM +0100, Jiri Olsa escreveu:
> On Mon, Nov 28, 2016 at 05:40:46PM -0200, Arnaldo Carvalho de Melo wrote:
>
> SNIP
>
> > CC /tmp/build/perf/builtin-buildid-list.o
> > LD /tmp/build/perf/pmu-events/pmu-events-in.o
> > CC /tmp/build/perf/arch/
On 11/29/2016 08:03 AM, David Howells wrote:
How about the attached? Obviously it need extending to other drivers.
This is great, I like it a lot better.
Reviewed-by: Corey Minyard
-corey
I thought that if I'm changing the module_param annotations anyway then it's
probably worth bunging i
On Tue, 29 Nov 2016, Marc Zyngier wrote:
> On 29/11/16 13:42, Thomas Gleixner wrote:
> > Assumptions w/o real impact are a perfect reason not to apply that
> > patch. This want's a proper proof that the global timer really changes and
> > this hackery is required, which I seriously doubt.
>
> Well
On Thu, Nov 17, 2016 at 10:47:28AM +0800, Xunlei Pang wrote:
> As per the comment, the code here only needs to flush context caches
> for the special domain 0 which is used to tag the
> non-present/erroneous caches, seems we should flush the old domain id
> of present entries for kdump according to
When CONFIG_SRAM is enable and the SRAM region is found, the entire SRAM
region resource is requested and marked as occupied by SRAM driver even
if certain parts of regions is marked reserved.
It's quite possible that a small region of the SRAM is reserved for all
the mailbox communication and hen
Currently the read operation on the message debug file returns error if
there's no data ready to be read. It expects the userspace to retry if
it fails. Since the mailbox response could be asynchronous, it would be
good to add support to block the read until the data is available.
We can also impl
On 11/25/2016, 05:18 PM, Guenter Roeck wrote:
> On 11/25/2016 12:30 AM, Jiri Slaby wrote:
>> This is the start of the stable review cycle for the 3.12.68 release.
>> There are 127 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being app
On Tue, Nov 29, 2016 at 12:33:15PM -0200, Arnaldo Carvalho de Melo wrote:
> Em Tue, Nov 29, 2016 at 03:28:08PM +0100, Jiri Olsa escreveu:
> > On Mon, Nov 28, 2016 at 05:40:46PM -0200, Arnaldo Carvalho de Melo wrote:
> >
> > SNIP
> >
> > > CC /tmp/build/perf/builtin-buildid-list.o
> > >
Commit aeefb36832e5 ("drm/exynos: gsc: add device tree support and remove
usage of static mappings") made the DRM_EXYNOS_GSC Kconfig symbol to only
be selectable if the exynos-gsc V4L2 driver isn't enabled, since both use
the same HW IP block.
But added the dependency as depends on !VIDEO_SAMSUNG_
On Tue 29-11-16 15:08:10, Thomas Gleixner wrote:
> On Mon, 28 Nov 2016, Michal Hocko wrote:
> > On Sun 27-11-16 00:13:36, Sebastian Andrzej Siewior wrote:
> > [...]
> > > static void __init init_cpu_node_state(void)
> > > {
> > > - int cpu;
> > > + int node;
> > >
> > > - for_each_online_cpu(cp
Hello Don,
On 10/13/2016 03:12 PM, Don Brace wrote:
>> -Original Message-
>> From: Javier Martinez Canillas [mailto:jav...@osg.samsung.com]
>> Sent: Thursday, October 13, 2016 11:11 AM
>> To: linux-kernel@vger.kernel.org
>> Cc: Javier Martinez Canillas; esc.storagedev; iss_storage...@hp.co
> So caveat that I'm ill and cannot think much..
>
> On Mon, Nov 28, 2016 at 11:26:46AM -0800, kan.li...@intel.com wrote:
>
> > Here, all the possible failure cases are listed.
> > Terms:
> > - new: current PMU counter value which read from rdpmcl.
> > - prev: previous counter value whi
On Tue, Nov 29, 2016 at 12:42:43PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 29, 2016 at 10:57:59AM +, Morten Rasmussen wrote:
> > > @@ -5708,13 +5708,6 @@ static int select_idle_cpu(struct task_struct *p,
> > > struct sched_domain *sd, int t
> > >
> > > avg_cost = this_sd->avg_scan_cost;
Em Tue, Nov 29, 2016 at 03:39:35PM +0100, Jiri Olsa escreveu:
> On Tue, Nov 29, 2016 at 12:33:15PM -0200, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Nov 29, 2016 at 03:28:08PM +0100, Jiri Olsa escreveu:
> > > On Mon, Nov 28, 2016 at 05:40:46PM -0200, Arnaldo Carvalho de Melo wrote:
> > >
> > > SN
On Tue, Nov 29, 2016 at 02:04:27PM +0100, Vincent Guittot wrote:
> On 29 November 2016 at 11:57, Morten Rasmussen
> wrote:
> > On Fri, Nov 25, 2016 at 04:34:32PM +0100, Vincent Guittot wrote:
> >> @@ -5708,13 +5708,6 @@ static int select_idle_cpu(struct task_struct *p,
> >> struct sched_domain *
Both iterations over online cpus can be replaced by the proper node
specific functions.
Cc: Andrew Morton
Cc: Vlastimil Babka
Cc: Mel Gorman
Cc: Johannes Weiner
Cc: linux...@kvack.org
Signed-off-by: Sebastian Andrzej Siewior
---
v1…v2: take into account that we may have online nodes with no C
On 29/11/16 14:32, Thomas Gleixner wrote:
> On Tue, 29 Nov 2016, Marc Zyngier wrote:
>> On 29/11/16 13:42, Thomas Gleixner wrote:
>>> Assumptions w/o real impact are a perfect reason not to apply that
>>> patch. This want's a proper proof that the global timer really changes and
>>> this hackery is
> 29 нояб. 2016 г., в 17:32, Thomas Gleixner написал(а):
>
> Can we just disable that global timer on affected SoCs and use something
> else instead?
I’ve sent patch series for fixing that on rockchip SoC.
http://lists.infradead.org/pipermail/linux-rockchip/2016-November/013217.html
But the se
Actually only the mvneta_bm support is not 64-bits compatible.
The mvneta code itself can run on 64-bits architecture.
Signed-off-by: Gregory CLEMENT
---
drivers/net/ethernet/marvell/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/Kconfi
Hello Wim,
On 10/20/2016 07:28 PM, Guenter Roeck wrote:
> On Wed, Oct 19, 2016 at 04:49:42PM -0300, Javier Martinez Canillas wrote:
>> The Amlogic Meson is a DT-only platform, which means the devices are
>> registered via OF and not using the legacy platform devices support.
>>
>> So there's no ne
On Tue, 2016-11-29 at 11:26 +0100, Andrey Konovalov wrote:
> On Sat, Nov 26, 2016 at 9:05 PM, Eric Dumazet wrote:
> >> I actually see multiple places where skb_network_offset() is used as
> >> an argument to skb_pull().
> >> So I guess every place can potentially be buggy.
> >
> > Well, I think th
Hi Dave,
if there's still time here's one more patch to 3.9. I think this is good
to have in 3.9 as it fixes an issue where we were printing uninitialised
memory in mwifiex. I had this in wireless-drivers already for some time
as I was waiting for other fixes and nothing serious actually came up.
From: Marcin Wojtas
Prepare the mvneta driver in order to be usable on the 64 bits platform
such as the Armada 3700.
[gregory.clem...@free-electrons.com]: this patch was extract from a larger
one to ease review and maintenance.
Signed-off-by: Marcin Wojtas
Signed-off-by: Gregory CLEMENT
---
From: Randy Dunlap [mailto:rdun...@infradead.org]
> > +void radix_tree_iter_replace(struct radix_tree_root *,
> > + const struct radix_tree_iter *, void **slot, void *item);
>
> > +int radix_tree_split(struct radix_tree_root *, unsigned long index,
> > + unsigned new_or
301 - 400 of 1099 matches
Mail list logo