This patchset contains the pwm support for the Broadcom's iProc SoC's.
The first patch provides the documentation details and the
second patch contains the controller support details. The third patch
contains the enable method for Northstar Plus SoC.
This patch series has been tested on NSP bcm95
On Wed 23 Mar 12:47 PDT 2016, Srinivas Kandagatla wrote:
> This patch adds support to gsbi1 uart and its pinctrls nodes.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-pins.dtsi | 14 ++
> arch/arm/boot/dts/qcom-apq8064.dtsi | 10 ++
> 2 f
On Tue, Mar 29, 2016 at 6:52 AM, Arnd Bergmann wrote:
> On Tuesday 29 March 2016 06:32:29 Tim Harvey wrote:
>> >
>> > There is no upstream driver for this chip, so I don't know where to look
>> > to find out if the driver tries to enable MSI.
>> >
>> > Is what you are saying that if you enable MSI
On Wed 23 Mar 12:47 PDT 2016, Srinivas Kandagatla wrote:
> This patch fixes pinctrls for spi and i2c nodes whose default and sleep
> states are together, which is incorrect.
>
> Without this patch i2c/spi would not be functional.
>
> Signed-off-by: Srinivas Kandagatla
The change in itself is s
On 29-03-16, 14:10, Rafael J. Wysocki wrote:
> In that case the loop will break for freq = 9000 (as per the above
> freq >= freq_target check), so it looks like you've misread it.
My bad ..
--
viresh
Thanks Bjorn,
On 27/03/16 06:50, Bjorn Andersson wrote:
On Wed 23 Mar 12:48 PDT 2016, Srinivas Kandagatla wrote:
This patch adds support to 4 user leds, wlan and bt led on board.
Signed-off-by: Srinivas Kandagatla
I'm not fond of the overly complicated names; and I think it should at
least
On Wed 23 Mar 18:48 PDT 2016, Stephen Boyd wrote:
> On 03/23/2016 06:04 PM, Bjorn Andersson wrote:
> > On Wed, Mar 23, 2016 at 1:30 PM, Srinivas Kandagatla
> > wrote:
> >>
> >> On 23/03/16 20:07, Stephen Boyd wrote:
[..]
> >
> > Also, if I make a product based of this board, with some minor
> > c
On Tue 29-03-16 22:45:40, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > From: Michal Hocko
> >
> > __alloc_pages_may_oom is the central place to decide when the
> > out_of_memory should be invoked. This is a good approach for most checks
> > there because they are page allocator specific and the
Add PWM support to the device tree for the Broadcom Northstar Plus SoC.
Signed-off-by: Yendapally Reddy Dhananjaya Reddy
---
arch/arm/boot/dts/bcm-nsp.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
index def9e78..f
On Tue, Mar 29, 2016 at 8:11 AM, Srinivas Kandagatla
wrote:
> On some SOCs PORTS_IMPL register value is never programmed by the BIOS
s/BIOS/firmware/
You do plan to fix this in your firmware/bootloader, too, right?
> and left at zero value. Which means that no sata ports are avaiable for
> soft
On 03/29/2016 04:56 AM, Steven Haigh wrote:
Interestingly enough, this just happened again - but on a different
virtual machine. I'm starting to wonder if this may have something to do
with the uptime of the machine - as the system that this seems to happen
to is always different.
Destroying it
Hi!
On Tue 2016-03-29 16:00:09, Oliver Neukum wrote:
> On Tue, 2016-03-29 at 15:06 +0200, Rafael J. Wysocki wrote:
> > On Monday, March 28, 2016 11:20:12 PM Pavel Machek wrote:
> > > Hi!
> > >
> > > Few releases ago, I could wake up PC from S3 sleep by hitting any
> > > key. That ceased to work s
On Tue 29-03-16 15:27:35, Michal Hocko wrote:
[...]
> If this looks like a reasonable approach I would go on think about how
> we can extend this for the oom_reaper and queue the current thread for
> the reaper to free some of the memory.
And this is what I came up with (untested yet). Doesn't too
On Tue, Mar 29, 2016 at 5:55 AM, Lucas Stach wrote:
> I would suspect that most boards specify the reset polarity the wrong
> way around. Fixing this without breaking DT stability is hard. OTOH we
It is not hard if we just revert the buggy commit.
> could just argue that the system description
On Wed, Mar 23 2016, Vlastimil Babka wrote:
> Hanjun Guo has reported that a CMA stress test causes broken accounting of
> CMA and free pages:
>
>> Before the test, I got:
>> -bash-4.3# cat /proc/meminfo | grep Cma
>> CmaTotal: 204800 kB
>> CmaFree: 195044 kB
>>
>>
>> After running
All CPUs on Tegra platform share clock/voltage lines and there is
absolutely no need of setting platform data for 'cpufreq-dt' platform
device, as that's the default case.
Stop setting platform data for cpufreq-dt device.
Signed-off-by: Viresh Kumar
---
Only compile tested.
drivers/cpufreq/teg
Yep, the rest of the patchset works fine without this patch
On Tue, 2016-03-29 at 10:27 +0200, Daniel Vetter wrote:
> On Mon, Mar 28, 2016 at 10:33:22AM -0400, Lyude wrote:
> >
> > This is part of a patch series to migrate all of the workarounds for
> > commonly seen behavior from bad sinks in in
From: Ludovic Desroches
So far, the CIDR and EXID registers were in the DBGU interface. This device
has disappeared with the SAMA5D2 family. These registers are exposed
through a new device called chipid.
Signed-off-by: Ludovic Desroches
[nicolas.fe...@atmel.com: remove useless warnings]
Acked-
I am announcing the release of the Linux 3.16.7-ckt26 kernel.
The updated 3.16.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.16.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.16.y
The diff from v3.16.7-ckt25 is posted
Le 29/03/2016 15:55, Arnd Bergmann a écrit :
> On Friday 18 March 2016 08:21:19 Ludovic Desroches wrote:
>> -struct soc_device * __init at91_soc_init(const struct at91_soc *socs)
>> +int __init at91_get_cidr_exid_from_dbgu(u32 *cidr, u32 *exid)
>> {
>
>
>> +
>> +int __init at91_get_cidr_exid_fro
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
> int perf_output_begin(struct perf_output_handle *handle,
> struct perf_event *event, unsigned int size
On Tue, 2016-03-29 at 15:06 +0200, Rafael J. Wysocki wrote:
> On Monday, March 28, 2016 11:20:12 PM Pavel Machek wrote:
> > Hi!
> >
> > Few releases ago, I could wake up PC from S3 sleep by hitting any
> > key. That ceased to work some time before, keyboard would just light a
> > NUM lock LED when
On Tue, Mar 29, 2016 at 01:11:55PM +0200, Arend Van Spriel wrote:
> Hi Al,
>
> Moved to 4.6-rc1 and found NFS mounts were failing moving to the new
> kernel. The NFS mounts are done using autofs. Below is the bisect log
> and attached the kernel .config file. Let me know if you need any other
> in
Hi Tony,
On 18/03/16 15:41, Grygorii Strashko wrote:
> On 03/17/2016 04:19 PM, Jon Hunter wrote:
>> The ARM TWD interrupt is a private peripheral interrupt (PPI) and per
>> the ARM GIC documentation, whether the type for PPIs can be set is
>> IMPLEMENTATION DEFINED. For OMAP4 devices the PPI type
On Tue, Mar 29, 2016 at 07:15:38AM -0500, Dinh Nguyen wrote:
> If you don't mind, I can take this patch. This will prevent merge
> conflicts in the
> DTS board files.
Fine with me as long as people don't start complaining if they start
testing my for-next branch and realize that the Arria10 suppor
Hi Geert,
On 29/03/16 14:04, Geert Uytterhoeven wrote:
> Hi Jon,
>
> On Thu, Mar 17, 2016 at 3:19 PM, Jon Hunter wrote:
>> --- a/drivers/irqchip/irq-gic.c
>> +++ b/drivers/irqchip/irq-gic.c
>
>> -#ifdef CONFIG_SMP
>> - set_smp_cross_call(gic_raise_softirq);
>> - regi
On Friday 18 March 2016 08:21:19 Ludovic Desroches wrote:
> -struct soc_device * __init at91_soc_init(const struct at91_soc *socs)
> +int __init at91_get_cidr_exid_from_dbgu(u32 *cidr, u32 *exid)
> {
> +
> +int __init at91_get_cidr_exid_from_chipid(u32 *cidr, u32 *exid)
> +{
>
These should bot
Hi Serge,
On Mon, Mar 21, 2016 at 06:41:33PM -0500, Serge E. Hallyn wrote:
> One practical problem I've found with cgroup namespaces is that there
> is no way to disambiguate between a cgroupfs mount which was done in
> a cgroup namespace, and a bind mount of a cgroupfs directory. So
> whether I
[ dropping my old email address ]
On 03/29/2016 02:58 PM, Michal Kubecek wrote:
On Mon, Feb 22, 2016 at 10:31:33AM -0500, Sasha Levin wrote:
I've hit the following warning while fuzzing with trinity inside a kvmtool guest
running the latest -next kernel:
[ 1343.104588] ===
Le 23/03/2016 14:47, Alexandre Belloni a écrit :
> On 23/03/2016 at 12:22:49 +0100, Nicolas Ferre wrote :
>> Le 18/03/2016 11:34, Alexandre Belloni a écrit :
>>> On 18/03/2016 at 08:21:19 +0100, Ludovic Desroches wrote :
So far, the CIDR and EXID registers were in the DBGU interface. This devi
On Tuesday 29 March 2016 06:32:29 Tim Harvey wrote:
> >
> > There is no upstream driver for this chip, so I don't know where to look
> > to find out if the driver tries to enable MSI.
> >
> > Is what you are saying that if you enable MSI support in the kernel, it
> > breaks legacy IRQs?
>
> Yes -
On Thu, 24 Mar 2016, Clément VUCHENER wrote:
> Thanks for the tip, is it possible to ignore some usages with this
> method (done in the default case)?
mapping to 0xff is a bit hackish way to achieve this.
--
Jiri Kosina
SUSE Labs
On 29/03/2016 at 15:32:06 +0200, Sebastian Andrzej Siewior wrote :
> * Alexandre Belloni | 2016-03-17 21:09:43 [+0100]:
>
> >Hi Sebastian,
> Hi Alexandre,
>
> >This patch fixes the last warning for preempt-rt on at91. It applies on
> >v4.4.4-rt11. Note that the whome PIT/TCB mess will be fixed in
On 29 March 2016 at 14:26, Matt Fleming wrote:
> On Mon, 21 Mar, at 08:31:59PM, Matt Fleming wrote:
>>
>> Good question. They're not handled in any special way with this patch
>> series, so the firmware will just initiate its own reset inside of
>> UpdateCapsule().
>>
>> That's probably not what w
On Mon, Mar 28, 2016 at 05:28:14PM -0700, Paul E. McKenney wrote:
> On Mon, Mar 28, 2016 at 05:25:18PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 28, 2016 at 06:08:41AM -0700, Paul E. McKenney wrote:
> > > On Mon, Mar 28, 2016 at 08:25:47AM +0200, Peter Zijlstra wrote:
> > > > On Sun, Mar 27, 2
Le 10/03/2016 14:31, Nicolas Ferre a écrit :
> Note to myself: change the $subject line to:
> ARM: dts: at91: sama5d2: add LCD controller
>
> :-)
With $subject changed, queued in at91-4.7-dt branch.
> Le 10/03/2016 14:25, Nicolas Ferre a écrit :
>> Add LCD controller node that binds to the atmel
Michal Hocko wrote:
> From: Michal Hocko
>
> __alloc_pages_may_oom is the central place to decide when the
> out_of_memory should be invoked. This is a good approach for most checks
> there because they are page allocator specific and the allocation fails
> right after.
>
> The notable exception
On Mon, 28 Mar 2016, Ping Cheng wrote:
> > Looks like recent changes in the Wacom driver made the Bamboo ONE crashes.
> > The tablet behaves as if it was a regular Bamboo device with pen, touch
> > and pad, but there is no physical pad connected to it.
> > The weird part is that the pad is still s
On Tue, 29 Mar 2016, Benjamin Tissoires wrote:
> > The lenovo_send_cmd_cptkbd function uses a stack variable to submit
> > commands via hid_hw_raw_request. Eventually this gets to the
> > usb_hcd_map_urb_for_dma function, which causes a warning to be thrown
> > if the CONFIG_DMA_API_DEBUG option
Le 29/03/2016 15:32, Sebastian Andrzej Siewior a écrit :
> * Alexandre Belloni | 2016-03-17 21:09:43 [+0100]:
>
>> Hi Sebastian,
> Hi Alexandre,
>
>> This patch fixes the last warning for preempt-rt on at91. It applies on
>> v4.4.4-rt11. Note that the whome PIT/TCB mess will be fixed in another w
On Mon, Mar 28, 2016 at 04:53:48PM -0700, Jeffrey Vander Stoep wrote:
> https://lkml.org/lkml/2016/2/23/812 "pipe: Fix buffer offset after
> partially failed read" is missing from the stable 3.4.y and 3.10.y
> kernels. It has been included in 3.2.y and 3.14.y.
>
> I am able to cause a kernel panic
* Alexandre Belloni | 2016-03-17 21:09:43 [+0100]:
>Hi Sebastian,
Hi Alexandre,
>This patch fixes the last warning for preempt-rt on at91. It applies on
>v4.4.4-rt11. Note that the whome PIT/TCB mess will be fixed in another way in
>the mainline as we are reworking the tcb driver to avoid using t
Le 29/03/2016 15:26, Sebastian Andrzej Siewior a écrit :
> Currently the driver will disable the clock and enable it one line later
> if it is switching from periodic mode into one shot.
> This can be avoided and causes a needless warning on -RT.
>
> Tested-by: Alexandre Belloni
> Acked-by: Alexa
On Tue, Mar 29, 2016 at 3:55 AM, Lucas Stach wrote:
> Am Dienstag, den 29.03.2016, 12:39 +0200 schrieb Krzysztof Hałasa:
>> Lucas Stach writes:
>>
>> > Is this working with v4.4 and PCI_MSI enabled? I'm sure I've tested MSI
>> > IRQs before enabling them in the defconfig and they have been workin
Thanks Nico,
On 24/03/16 16:51, Nicolas Dechesne wrote:
On Wed, Mar 23, 2016 at 8:48 PM, Srinivas Kandagatla
wrote:
+ led@1 {
+ label = "dragonboard-600c:green:user1";
+ gpios = <&tlmm_pinmux 3 GPIO_ACTIVE_HIGH>;
Hi Mark,
On Tue, 2016-03-29 at 03:11 +0800, Mark Brown wrote:
> On Fri, Mar 25, 2016 at 11:42:05AM +0800, PC Liao wrote:
>
> > +Optional properties:
> > +- mediatek,rt5650_i2s: I2S mode of rt5650
> > + 0: using I2S1 on rt5650 for record
> > + 1: using I2S2 on rt5650 for record
> > +
>
> I woul
On Tuesday 29 March 2016 21:21:49 Zhangjian wrote:
> >>>
> >>> Then we could remove the __USE_FILE_OFFSET64 in stat.h and fcnt.h in
> >>> aarch64. And truncate and ftruncate is same as truncate64 and
> >>> ftruncate64.
> >>
> >> I don't know what the glibc developers prefer, but I think the
> >> re
From: Michal Hocko
__alloc_pages_may_oom is the central place to decide when the
out_of_memory should be invoked. This is a good approach for most checks
there because they are page allocator specific and the allocation fails
right after.
The notable exception is GFP_NOFS context which is faking
Hi Yakir,
On 29 March 2016 at 12:40, Yakir Yang wrote:
> Hi Emil,
>
> On 03/28/2016 08:21 PM, Emil Velikov wrote:
>>
>> On 22 March 2016 at 00:42, Heiko Stuebner wrote:
>>>
>>> Hi Yakir,
>>>
>>> Am Montag, 21. März 2016, 20:17:46 schrieb Yakir Yang:
On 03/21/2016 07:29 PM, Heiko Stübne
On Tue, 2016-03-29 at 12:34 +0200, Ingo Molnar wrote:
> * Toshi Kani wrote:
>
> > A Xorg failure on qemu32 was reported as a regression [1] caused by
> > 'commit 9cd25aac1f44 ("x86/mm/pat: Emulate PAT when it is disabled")'.
> > This patch-set fixes the regression.
> >
> > Negative effects of th
Currently the driver will disable the clock and enable it one line later
if it is switching from periodic mode into one shot.
This can be avoided and causes a needless warning on -RT.
Tested-by: Alexandre Belloni
Acked-by: Alexandre Belloni
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/
On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>
> In addition, I wonder how explicit and implicit fences could coexist together.
> Rob said,
> "Implicit sync ofc remains the default, but userspace could opt-in to
> explicit sync instead"
>
> This would mean that if we use explicit sync for us
On 03/29/2016 02:52 PM, Vineet Gupta wrote:
On Monday 21 March 2016 07:54 PM, Noam Camus wrote:
From: Noam Camus
Add internal tick generator which is shared by all cores.
Each cluster of cores view it through dedicated address.
This is used for SMP system where all CPUs synced by same
clock so
Hi, Yury
On 2016/3/29 20:01, Yury Norov wrote:
On Tue, Mar 29, 2016 at 12:58:25PM +0200, Arnd Bergmann wrote:
On Saturday 26 March 2016 20:36:43 Zhangjian wrote:
Hi, Arnd
On 2016/3/21 17:43, Arnd Bergmann wrote:
On Monday 21 March 2016 10:07:49 Andreas Schwab wrote:
This patch may fix a few
This driver sets the broadcast tick quite early on during probe and does
not clean up again in cast of failure. This patch moves the setup call
after the registration, placing the on_each_cpu() calls within the global
CPU lock region.
Cc: Len Brown
Cc: linux...@vger.kernel.org
Signed-off-by: Ric
The helper function, intel_idle_cpu_init, registers one new device
with the cpuidle layer. If the registration should fail, that
function immediately calls intel_idle_cpuidle_devices_uninit() to
unregister every last CPU's device. However, it makes no sense to do
so, when called from the hot plug
The function, intel_idle_cpuidle_driver_init, delivers no error codes
at all. This patch changes the function to return 'void' instead of
returning zero.
Cc: Len Brown
Cc: linux...@vger.kernel.org
Signed-off-by: Richard Cochran
---
drivers/idle/intel_idle.c | 4 +---
1 file changed, 1 insertio
Cc: Len Brown
Cc: linux...@vger.kernel.org
Signed-off-by: Richard Cochran
---
drivers/idle/intel_idle.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
index ba947df..9d5ed32 100644
--- a/drivers/idle/intel_idle.c
+++ b/drivers/idle/inte
In the module_exit() method, this driver first frees its per-CPU
pointer, then unregisters a callback making use of the pointer.
Furthermore, the function, intel_idle_cpuidle_devices_uninit, is racy
against CPU hot plugging as it calls for_each_online_cpu().
This patch corrects the issues by unreg
These chips has an almost identical interface but a deal with a
different number of value bits. Datasheet links for comparison:
* http://www.ti.com/lit/ds/symlink/adc081c021.pdf
* http://www.ti.com/lit/ds/symlink/adc101c021.pdf
* http://www.ti.com/lit/ds/symlink/adc121c021.pdf
I am working wit
This driver has one serious and one mild bug in its hot plug handling.
First, whenever a new CPU goes on line, if the call to
cpuidle_register_driver() should fail (say, due to lack of memory),
then the driver frees its per-CPU region. On the *next* CPU_ONLINE
event, the driver will happily use t
If a cpuidle registration error occurs during the hot plug notifier
callback, we should really inform the hot plug machinery instead of
just ignoring the error. This patch changes the callback to properly
return on error.
Cc: Len Brown
Cc: linux...@vger.kernel.org
Signed-off-by: Richard Cochran
The helper function, intel_idle_cpuidle_devices_uninit, frees the
globally allocated per-CPU data. However, this function is invoked
from the hot plug notifier callback at a time when freeing that data
is not safe.
If the call to cpuidle_register_driver() should fail (say, due to lack
of memory),
This driver registers cpuidle devices when a CPU comes online, but it
leaves the registrations in place when a CPU goes offline. The module
exit code only unregisters the currently online CPUs, leaving the
devices for offline CPUs dangling.
This patch changes the driver to clean up all registrati
In the module_init() method, if the per-CPU allocation fails, then the
active cpuidle registration is not cleaned up. This patch fixes the
issue by attempting the allocation before registration, and then
cleaning it up again on registration failure.
Cc: Len Brown
Cc: linux...@vger.kernel.org
Sig
The function, intel_idle_cpuidle_driver_init, makes calls on each CPU
to auto_demotion_disable() and c1e_promotion_disable(). These calls
are redundant, as intel_idle_cpu_init() does the same calls just a bit
later on. They are also premature, as the driver registration may yet
fail.
This patch
[Re: [PATCH 4/4] drivers/bus: make arm-ccn.c driver explicitly non-modular] On
29/03/2016 (Tue 12:53) Pawel Moll wrote:
> Dnia 2016-03-29, Tue o godzinie 12:45 +0100, Will Deacon pisze:
> > I'd much rather fix the driver to build as a module, if at all
> > possible.
> > Suzuki (CC'd) is taking a
* Ingo Molnar wrote:
> That's a totally useless analysis of task_struct::flags, while we want to
> convert thread_info::flags...
So going over to arguing about thread_info::flags:
1)
We already have ti::flags accessors for most of the generic code. There's a few
outliers (in the scheduler c
On 28 March 2016 at 23:13, Heiko Stübner wrote:
> I have the feeling we're going quite a bit off-topic right now :-) .
> The binary-driver-crazyness, hasn't really anything to do with Yakir's support
> for the RGA (which is about raster-graphics-acceleration, so 2d stuff).
>
> And me mentioning t
On Tuesday 29 March 2016 12:55:21 Lucas Stach wrote:
> Am Dienstag, den 29.03.2016, 12:39 +0200 schrieb Krzysztof Hałasa:
> > Lucas Stach writes:
> >
> > > Is this working with v4.4 and PCI_MSI enabled? I'm sure I've tested MSI
> > > IRQs before enabling them in the defconfig and they have been w
In usecases where force_port_map is used saved_port_map is never set,
resulting in not programming the PORTS_IMPL register as part of intial
config. This patch fixes this by setting it to port_map even in case
where force_port_map is used, making it more inline with other parts of
the code.
Signed
On Tue, 2016-03-29 at 13:30 +0100, Will Deacon wrote:
> On Tue, Mar 29, 2016 at 12:53:06PM +0100, Pawel Moll wrote:
> > Dnia 2016-03-29, Tue o godzinie 12:45 +0100, Will Deacon pisze:
> > > I'd much rather fix the driver to build as a module, if at all
> > > possible.
> > > Suzuki (CC'd) is taking
This patch adds new ports-implemented mask, which is required to get
achi working on the mainline. Without this patch value read from
PORTS_IMPL register which is zero would not enable any ports for
software to use.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064.dtsi | 1 +
On some SOCs PORTS_IMPL register value is never programmed by the BIOS
and left at zero value. Which means that no sata ports are avaiable for
software. AHCI driver used to cope up with this by fabricating the
port_map if the PORTS_IMPL register is read zero, but recent patch
broke this workaround
Hi Tejun,
On some SOCs PORTS_IMPL register value is never programmed by the BIOS
and left at zero value. Which means that no sata ports are available for
software. AHCI driver used to cope up with this by fabricating the
port_map if the PORTS_IMPL register is read zero, but recent patch [1]
broke
On Monday, March 28, 2016 11:18:05 AM Darren Hart wrote:
> On Mon, Mar 28, 2016 at 05:18:39PM +0100, Colin King wrote:
> > From: Colin Ian King
> >
> > intel_menlow_memory_remove sanity checks to see if device is null, however,
> > this check is performed after we have already passed device into
On Monday, March 28, 2016 10:33:09 AM Darren Hart wrote:
> On Thu, Mar 24, 2016 at 12:24:56PM +0100, Gabriele Mazzotta wrote:
> > 2016-03-24 10:39 GMT+01:00 Pali Rohár :
> > > On Monday 21 March 2016 16:13:34 Gabriele Mazzotta wrote:
> > >> 2016-03-21 13:17 GMT+01:00 Pali Rohár :
> > >> > On Friday
On Tue, Mar 29, 2016 at 03:05:14PM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> >
> > * Linus Torvalds wrote:
> >
> > > On Tue, Mar 29, 2016 at 4:44 AM, Ingo Molnar wrote:
> > > >
> > > > Harmonizing thread_info::flags does not look easy, given how much
> > > > assembly code
> > >
On Thursday 24 March 2016 17:49:57 Neil Armstrong wrote:
> This serie adds initial support (IRQ, Timer, GPIO, Reset, Serial, Clocks) for
> the PLX Technology OX810SE used in the well-known Western Digital My Book
> World Edition Network Attached Storage device.
>
> Extended support for SATA, DMA a
On 03/25/2016 08:22 PM, Andrew Morton wrote:
On Fri, 25 Mar 2016 14:56:04 +0800 Xishi Qiu wrote:
It is incorrect to use next_node to find a target node, it will
return MAX_NUMNODES or invalid node. This will lead to crash in
buddy system allocation.
...
--- a/mm/page_isolation.c
+++ b/mm/pag
* Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Tue, Mar 29, 2016 at 4:44 AM, Ingo Molnar wrote:
> > >
> > > Harmonizing thread_info::flags does not look easy, given how much
> > > assembly code
> > > accesses this field.
> >
> > It might not be too bad.
> >
> > For 32-bit archi
On Tue, 29 Mar 2016, Miroslav Benes wrote:
> > 1) Jessica proposed using the Arch-independent patchset ensure that
> > livepatch
> > finishes writing its relas before apply_paravirt() is called. However, this
> > introduces a bit more arch-dependent code. It would be useful to see if
> > other
>
On Monday, March 28, 2016 11:20:12 PM Pavel Machek wrote:
> Hi!
>
> Few releases ago, I could wake up PC from S3 sleep by hitting any
> key. That ceased to work some time before, keyboard would just light a
> NUM lock LED when I hit a key (4.5). Now PC seems to be sleeping (in
> S3) with NUM lock
Hi Jon,
On Thu, Mar 17, 2016 at 3:19 PM, Jon Hunter wrote:
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> -#ifdef CONFIG_SMP
> - set_smp_cross_call(gic_raise_softirq);
> - register_cpu_notifier(&gic_cpu_notifier);
> -#endif
> + if (gic_n
On Thursday 24 March 2016 17:50:11 Neil Armstrong wrote:
> Add Kconfig support for mach-oxnas.
>
> Signed-off-by: Neil Armstrong
>
Please merge this into patch 13, no need to keep those separate.
For the subject line, please use 'ARM' as the prefix, not 'arm'.
Arnd
A failed call to dqget() returns an ERR_PTR() and not null. Fix
the check in ext4_ioctl_setproject() to handle this correctly.
Fixes: 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface
support")
Cc: sta...@vger.kernel.org # v4.5
Signed-off-by: Seth Forshee
---
fs/ext4/ioctl.
[ adding CCs ]
On Tue, 29 Mar 2016, Chris J Arges wrote:
> Paravirtualized ops and livepatching currently don't mix very well and can
> cause undefined behavor such as oops, invalid opcodes or corrupted stacks.
> The original discussion of this issue can be found here [1].
>
> I've written an e
* Linus Torvalds wrote:
> On Tue, Mar 29, 2016 at 4:44 AM, Ingo Molnar wrote:
> >
> > Harmonizing thread_info::flags does not look easy, given how much assembly
> > code
> > accesses this field.
>
> It might not be too bad.
>
> For 32-bit architectures (which is still most of them), it's jus
On Tue, 2016-03-29 at 17:27 +0800, Wei-Ning Huang wrote:
> Adding some chromium devs to the thread.
>
> In, http://lxr.free-electrons.com/source/mm/page_alloc.c#L3152
>
> The default mm retry allocation when 'order <=
> PAGE_ALLOC_COSTLY_ORDER' of gfp_mask contains __GFP_REPEAT.
> PAGE_ALLOC_COST
On Mon, Feb 22, 2016 at 10:31:33AM -0500, Sasha Levin wrote:
>
> I've hit the following warning while fuzzing with trinity inside a kvmtool
> guest
> running the latest -next kernel:
>
> [ 1343.104588] ===
> [ 1343.104591] [ INFO: suspicious RCU usage. ]
> [ 1343.1046
On 3/29/2016 8:44 AM, Stefano Stabellini wrote:
> Could you please explain what is the problem that you are trying to
> solve? In other words, what is the issue with assuming that physical
> address = dma address (and the current dma_to_phys and phys_to_dma
> static inlines) if no arm64 platforms v
On Monday 21 March 2016 07:54 PM, Noam Camus wrote:
> From: Noam Camus
>
> Adding EZchip NPS400 support.
> NPS internal interrupts are internally handled at
> Multi Thread Manager (MTM) that is signaled for deactivating
> an interrupt.
> External interrupts is handled also at Global Interrupt
> C
On Monday, March 28, 2016 02:33:33 PM Viresh Kumar wrote:
> On 22-03-16, 02:54, Rafael J. Wysocki wrote:
> > Index: linux-pm/kernel/sched/cpufreq_schedutil.c
> > ===
> > --- /dev/null
> > +++ linux-pm/kernel/sched/cpufreq_schedutil.c
>
On Tue, Mar 29, 2016 at 02:54:23PM +0200, Peter Zijlstra wrote:
> +++ b/kernel/events/core.c
> @@ -4346,7 +4346,7 @@ static long _perf_ioctl(struct perf_even
>
> rcu_read_lock();
> rb = rcu_dereference(event->rb);
> - if (!event->rb) {
> + if (!
On Mon, Mar 28, 2016 at 06:41:29AM +, Wang Nan wrote:
> Add new ioctl() to pause/resume ring-buffer output.
>
> In some situations we want to read from ring buffer only when we
> ensure nothing can write to the ring buffer during reading. Without
> this patch we have to turn off all events att
Thanks for your comment, I think I can change it to val[0] | (val[1]
<< 8), is it okay ?
2016-03-29 20:06 GMT+08:00 Phil Reid :
> G'day Yong,
>
> One comment below.
>
> On 29/03/2016 2:27 PM, Yong Li wrote:
>>
>> The current implementation only uses the first byte in *val,
>> the second data is al
Michal Hocko wrote:
> From: Michal Hocko
>
> bb29902a7515 ("oom, oom_reaper: protect oom_reaper_list using simpler
> way") has simplified the check for tasks already enqueued for the oom
> reaper by checking tsk->oom_reaper_list != NULL. This check is not
> sufficient because the tsk might be the
On Thu, 24 Mar, at 04:15:56PM, Stanacar, Stefan wrote:
>
> Ok, that's funny somehow... I wouldn't be surprised if I'd find 3 more
> variations of the same driver in different vendor trees :(.
Right. And that does add weight to getting a version merged upstream;
to discourage people carrying their
On Tue, Mar 29, 2016 at 09:12:38AM +, Alexey Brodkin wrote:
> Hi Daniel,
>
> On Tue, 2016-03-29 at 10:19 +0200, Daniel Vetter wrote:
> > On Wed, Mar 23, 2016 at 01:41:05PM +, Alexey Brodkin wrote:
> > >
> > > Hi David,
> > >
> > > On Wed, 2016-03-23 at 12:13 +0100, David Herrmann wrote:
On Monday 21 March 2016 07:54 PM, Noam Camus wrote:
> From: Noam Camus
>
> Add internal tick generator which is shared by all cores.
> Each cluster of cores view it through dedicated address.
> This is used for SMP system where all CPUs synced by same
> clock source.
>
> Signed-off-by: Noam Camu
601 - 700 of 1022 matches
Mail list logo
