On 03/12, Andy Lutomirski wrote:
>
> Patch 1 is IMO a bug fix.
And personally I agree.
I am still not sure about renames in include/uapi, perhaps someone can
ack comment this change...
Perhaps we could could even do
- __u16 __pad0;
+ // comment to explain that ->ss i
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 1ca7b86062ec8473d03c5cdfd336abc8b1c8098c
Exit right away, when the removed waiter was not the top priority
waiter on the lock. Get rid of the extra
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: af54d6a1c3ad474bbc9893c9905022646be6092c
futex_lock_pi_atomic() is a maze of retry hoops and loops.
Reduce it to simple and understandable states:
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index a328b97369c2..50cab880b71
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Josh Cartwright
"lockdep: Selftest: Only do hardirq context test for raw spinlock"
disabled the execution of certain tests with PREEMPT_RT_FULL, but did
not prevent the tests from sti
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
Shrug. Lots of hobbyists have a beast in their basement, right?
Cc: stable...@vger.kernel.org
Signed-off-by: Mike Galbraith
Signed-off-by: Sebastian Andrzej Siewio
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 8de253240c16..29791c9d77a3
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This patch converts gpio_bank.lock from a spin_lock into a
raw_spin_lock. The call path is to access this lock is always under a
raw_spin_lock, for instance
On Fri, Mar 13, 2015 at 01:45:49AM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> pnpacpi_add_device() calls acpi_bind_one() on an already registered
> device, which is a mistake, but it can initialize the ACPI companion
> field of the struct device to be registered using ACPI_COMP
On Tue, Mar 10, 2015 at 4:47 AM, Tim Kryger wrote:
> On Mon, Mar 9, 2015 at 8:05 AM, Alan Cox wrote:
>
>> Ah no - I meant what is their official software workaround for existing
>> parts with the bug ? Presumably they have an errata document that
>> discusses this and the correct methods they rec
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: ccf9e6a80d9e1b9df69c98e6b9745cf49869ee15
The kernel tries to atomically unlock the futex without checking
whether there is kernel state associated t
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
Shrug. Lots of hobbyists have a beast in their basement, right?
Cc: stable...@vger.kernel.org
Signed-off-by: Mike Galbraith
Signed-off-by: Sebastian Andrzej Siewior
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 04e1b2e52b17195c9a1daa5935c55a4c8716095c
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the co
3.2.68-rt99-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
|BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:915
|in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd
|Preemption disabled
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Josh Cartwright
"lockdep: Selftest: Only do hardirq context test for raw spinlock"
disabled the execution of certain tests with PREEMPT_RT_FULL, but did
not prevent the tests from s
On Thu, Mar 12, 2015 at 9:34 PM, Fabian Frederick wrote:
> directly return recover_head() and ubifs_leb_unmap()
> instead of storing value in err and testing it.
>
> Signed-off-by: Fabian Frederick
Acked-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterh
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
|BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:915
|in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd
|Preemption disabl
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: a57594a13a446d1a6ab1dcd48339f799ce586843
Add a separate local variable for the boost/deboost logic to make the
code more readable. Add comments wher
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
Both pi_stress and sigwaittest in rt-test show performance gain with
__HAVE_ARCH_CMPXCHG. Testing result on coretile_express_a9x4:
pi_stress -p 99 --duration=300 (on linux-3.4-rc5; bigger
Hi,
On Friday 13 March 2015 08:45 PM, Nishanth Menon wrote:
On 03/13/2015 10:12 AM, Kishon Vijay Abraham I wrote:
Added a new compatible string "ti,am437x-ocp2scp" for OCP2SCP module.
This is needed since except for the OCP2SCP used in AM437x, SYNC2 value
in OCP2SCP TIMING should be changed whe
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 3eb65aeadf701976b084e9171e16bb7d1e83fbb0
Add commentry to document the chain walk and the protection mechanisms
and their scope.
Signed-off-by: Tho
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 2ffa5a5cd2fe792b6399c903d5172adf088d8ff7
There is no point to keep the task ref across the check for lock
owner. Drop the ref before that, so the pr
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 04e1b2e52b17195c9a1daa5935c55a4c8716095c
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the c
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: bd1dbcc67cd2c1181e2c01daac51eabf1b964dd8
No point in open coding the same function again.
Signed-off-by: Thomas Gleixner
Reviewed-by: Darren Hart
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This patch converts gpio_bank.lock from a spin_lock into a
raw_spin_lock. The call path is to access this lock is always under a
raw_spin_lock, for instance
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Steven Rostedt
To ease backporting patches, replace the plist functions with
rt_mutex_enqueue{_pi}() and rt_mutex_dequeue{_pi}() like upstream -rt does.
This will lower the conflicts
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
With task_blocks_on_rt_mutex() returning early -EDEADLK we never add the
waiter to the waitqueue. Later, we try to remove it via remove_waiter()
and go boom
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 67792e2cabadbadd1a93f6790fa7bcbd47eca7c3
In case the dead lock detector is enabled we follow the lock chain to
the end in rt_mutex_adjust_prio_chain
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
The ARM UP implementation of futex_atomic_cmpxchg_inatomic() assumes that
pagefault_disable() inherits a preempt disabled section. This assumtion
is true fo
On Mon, Mar 2, 2015 at 12:49 AM, Wang Long wrote:
> Remove the duplicate of_changeset_init. In of_selftest_changeset
> testcase, the "struct of_changeset chgset" is initialized twice,
> but only once is enough. so, drop the first initializtion code.
>
> Signed-off-by: Wang Long
Applied for 4.0.
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 8930ed80f970a90a795239e7415c9b0e6f964649
The conditions under which deadlock detection is conducted are unclear
and undocumented.
Add constants ins
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: af54d6a1c3ad474bbc9893c9905022646be6092c
futex_lock_pi_atomic() is a maze of retry hoops and loops.
Reduce it to simple and understandable states:
On Mon, Mar 2, 2015 at 9:50 PM, Wang Long wrote:
> This patch fix the wrong expected value of of_property_match_string
> in of_selftest_property_string.
>
> Signed-off-by: Wang Long
Applied for 4.0. Thanks.
Rob
> ---
> drivers/of/unittest.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 delet
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Daniel Wagner
Provides a framework for enqueuing callbacks from irq context
PREEMPT_RT_FULL safe. The callbacks are executed in kthread context.
Bases on wait-simple.
Signed-off-by
On 03/10/2015 01:01 PM, Bjorn Helgaas wrote:
From my point of view (far outside the networking world and completely
incompetent to judge the merits of XIA), this email seems like a
reasonable starting point for a discussion, and I'm disappointed that
it got shut down so fast. It might not be in
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
Both pi_stress and sigwaittest in rt-test show performance gain with
__HAVE_ARCH_CMPXCHG. Testing result on coretile_express_a9x4:
pi_stress -p 99 --duration=300 (on linux-3.4-rc5; bigger i
Le 12/03/2015 15:54, Alexandre Belloni a écrit :
> This series removes more mach/headers.
>
> Then it introduces a more scalable SoC detection infrastructure which allows
> to
> remove the at91_map_io/at91_alt_map_io and iotable_init ugliness.
>
> Changes in v4:
> - Changes soc family and name
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
upstream commit: fff421580f512fc044cc7421fdff31a7a6997350
Currently, the tvec_base structure's ->active_timers field tracks only
the non-deferrable timers, which
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
|BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:915
|in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd
|Preemption disable
On Mon, Feb 16, 2015 at 12:27 AM, Matwey V. Kornilov wrote:
> The whole menu already depends on OF, so there is no need to additionaly
> specify it.
>
> Suggested-by: Paul Bolle
> Signed-off-by: Matwey V. Kornilov
Applied for 4.0. Thanks.
Rob
> ---
> drivers/of/Kconfig | 1 -
> 1 file chang
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: e60cbc5ceaa518d630ab8f35a7d05cee1c752648
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the
Dear RT Folks,
This is the RT stable review cycle of patch 3.4.106-rt132-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release ca
On Fri, 13 Mar 2015 11:11:35 -0400
Steven Rostedt wrote:
> On Fri, Mar 13, 2015 at 05:49:13AM +0100, Mike Galbraith wrote:
> > On Thu, 2015-03-12 at 15:13 -0400, Steven Rostedt wrote:
> > > Dear RT Folks,
> > >
> > > This is the RT stable review cycle of patch 3.14.34-rt32-rc1.
> > >
> > > Plea
On Fri, Mar 13, 2015 at 03:39:28PM +0100, Oleg Nesterov wrote:
> This too needs cleanups. But later ;)
>
> Note that xstate_enable_boot_cpu is not called if !cpu_has_xsave, see the
> check in xsave_init(). Howver, eagerfpu=on will force eager_fpu_init() which
> calls eager_fpu_init_bp().
Yahaa.
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
mm, memcg: make refill_stock() use get_cpu_light()
Nikita reported the following memcg scheduling while atomic bug:
Call Trace:
[e22d5a90] [c0007ea8] show_stack+0x4c
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: bd1dbcc67cd2c1181e2c01daac51eabf1b964dd8
No point in open coding the same function again.
Signed-off-by: Thomas Gleixner
Reviewed-by: Darren Hart
On Fri, Mar 6, 2015 at 12:59 PM, Peter Hurley wrote:
> On 03/06/2015 01:11 PM, Peter Hurley wrote:
>> On 03/06/2015 11:52 AM, Leif Lindholm wrote:
>
> [...]
>
>>> Could you give the below a spin, and if it works for you, send me the
>>> above tests as a full patch so that I can post both as a seri
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 67792e2cabadbadd1a93f6790fa7bcbd47eca7c3
In case the dead lock detector is enabled we follow the lock chain to
the end in rt_mutex_adjust_prio_chai
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: c051b21f71d1ffdfd7ad406a1ef5ede5e5f974c5
The deadlock logic is only required for futexes.
Remove the extra arguments for the public functions and
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
With task_blocks_on_rt_mutex() returning early -EDEADLK we never add the
waiter to the waitqueue. Later, we try to remove it via remove_waiter()
and go boo
On Wed, Feb 18, 2015 at 4:29 PM, Niklas Cassel wrote:
> Signed-off-by: Niklas Cassel
> ---
> [PATCH 1/2] of this patch series has already reached its way into mainline.
> It would be nice if someone picked up [PATCH 2/2] (this commit) before the
> merge window closes.
>
> .../devicetree/binding
On Mon, Feb 16, 2015 at 12:27 AM, Matwey V. Kornilov wrote:
> Add prompt for OF_OVERLAY config option to make in visible in
> menuconfig/xconfig
> to make user be able to set or unset this option.
>
> Signed-off-by: Matwey V. Kornilov
Applied for 4.0. Thanks.
Rob
> ---
> Changes from v1:
> -
On 03/12, Andy Lutomirski wrote:
>
> What's wrong with off-topic? :)
OK ;)
> As vvar demonstrates, it's possible to add new per-process vmas that
> show up in all processes automatically. The trickiest part is making
> it work with CRIU.
Ah... I seem to finaly understand why exactly you added t
On Fri 13-03-15 19:55:27, Vaibhav Shinde wrote:
> On low memory situation, I see various shrinkers being invoked, but in
> lowmem_shrink() case, kswapd is found to be hogging for around 150msecs.
>
> Due to this my application suffer latency issue, as the cpu was not
> released by kswapd0.
>
> I
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 8930ed80f970a90a795239e7415c9b0e6f964649
The conditions under which deadlock detection is conducted are unclear
and undocumented.
Add constants in
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Steven Rostedt
To ease backporting patches, replace the plist functions with
rt_mutex_enqueue{_pi}() and rt_mutex_dequeue{_pi}() like upstream -rt does.
This will lower the conflict
On Tue, Mar 10, 2015 at 10:31 PM, Guenter Roeck wrote:
> sparc:allmodconfig fails to build with:
>
> drivers/built-in.o: In function `platform_bus_init':
> (.init.text+0x3684): undefined reference to
> `of_platform_register_reconfig_notifier'
>
> of_platform_register_reconfig_notifier is only dec
On Thu, Mar 5, 2015 at 9:53 AM, Matt Porter wrote:
> The exact steps provided for submitting binding patches can be read
> as requiring the bindings to be sent only to the devicet...@vger.kernel.org
> list. Since the DT maintainers would like to be Cced on any binding
> submissions, make this requ
On Thu, Feb 12, 2015 at 2:38 AM, Michal Simek wrote:
> PATA(pata_arasan_cf.c) and SDHCI(sdhci-of-arasan.c) drivers
> are already using this prefix.
>
> Signed-off-by: Michal Simek
Applied for 4.0. Thanks.
Rob
> ---
>
> https://arasan.com/contact/
> ---
> Documentation/devicetree/bindings/vend
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: ccf9e6a80d9e1b9df69c98e6b9745cf49869ee15
The kernel tries to atomically unlock the futex without checking
whether there is kernel state associated
On Wed, Mar 4, 2015 at 1:49 PM, Arnd Bergmann wrote:
> On Wednesday 04 March 2015 16:04:23 Geert Uytterhoeven wrote:
>> > - depends on OF_IRQ && OF_EARLY_FLATTREE
>> > + depends on OF_IRQ && OF_EARLY_FLATTREE && I2C=y && I2C_MUX=y
>>
>> ... I think it would be better to replace "#if IS
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 1ca7b86062ec8473d03c5cdfd336abc8b1c8098c
Exit right away, when the removed waiter was not the top priority
waiter on the lock. Get rid of the extra
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 358c331f391f3e0432f4f96f25017d12ac8d10b1
The current implementation of try_to_take_rtmutex() is correct, but
requires more than a single brain twis
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 04e1b2e52b17195c9a1daa5935c55a4c8716095c
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This patch converts gpio_bank.lock from a spin_lock into a
raw_spin_lock. The call path is to access this lock is always under a
raw_spin_lock, for instanc
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream-commit: 88f2b4c15e561bb5c28709d666364f273bf54b98
Oleg noticed that rtmutex_slowtrylock() has a pointless check for
rt_mutex_owner(lock) != current.
To avo
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: e60cbc5ceaa518d630ab8f35a7d05cee1c752648
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the w
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 7d028f4a9e56..5449cd22a524
On Fri, Mar 13, 2015 at 03:48:40PM +0100, Andrew Lunn wrote:
> On Fri, Mar 13, 2015 at 02:19:26PM +, Russell King - ARM Linux wrote:
> > On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote:
> > > Variable 'gephy' is assigned a value that is never used.
> > >
> > > Signed-off-by :
> > >
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: a57594a13a446d1a6ab1dcd48339f799ce586843
Add a separate local variable for the boost/deboost logic to make the
code more readable. Add comments whe
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
The ARM UP implementation of futex_atomic_cmpxchg_inatomic() assumes that
pagefault_disable() inherits a preempt disabled section. This assumtion
is true f
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
upstream commit: 16d937f880312e3f47157d4d6d6ebf7e61523378
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Paul Gortmaker
On 3.14-rt we see the following trace on Canoe Pass for
SCSI_ISCI "Intel(R) C600 Series Chipset SAS Controller"
when the sas qc_issue handler is run:
BUG: sleeping f
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 3eb65aeadf701976b084e9171e16bb7d1e83fbb0
Add commentry to document the chain walk and the protection mechanisms
and their scope.
Signed-off-by: Th
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
upstream commit: d550e81dc0ddc04f1b417c179c214103a28e0ee8
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the
3.4.106-rt132-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream commit: 2ffa5a5cd2fe792b6399c903d5172adf088d8ff7
There is no point to keep the task ref across the check for lock
owner. Drop the ref before that, so the p
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Josh Cartwright
"lockdep: Selftest: Only do hardirq context test for raw spinlock"
disabled the execution of certain tests with PREEMPT_RT_FULL, but did
not prevent the tests from st
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
upstream commit: 18d8cb64c9c074cbe2bd677ab10fff8283abdb62
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the
Dear RT Folks,
This is the RT stable review cycle of patch 3.10.70-rt75-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release can
On 03/13/2015 10:12 AM, Kishon Vijay Abraham I wrote:
> Added a new compatible string "ti,am437x-ocp2scp" for OCP2SCP module.
> This is needed since except for the OCP2SCP used in AM437x, SYNC2 value
> in OCP2SCP TIMING should be changed whereas the default value is sufficient
> in AM437x.
>
> Cc:
The 2nd memset() argument '286331153' doesn't fit into an 'unsigned char'.
Signed-off-by :
---
drivers/dma/iop-adma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/iop-adma.c b/drivers/dma/iop-adma.c
index 263d9f6..78382b0 100644
--- a/drivers/dma/iop-adma.c
+++
3.10.70-rt75-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
upstream-commit: 88f2b4c15e561bb5c28709d666364f273bf54b98
Oleg noticed that rtmutex_slowtrylock() has a pointless check for
rt_mutex_owner(lock) != current.
To avoi
3.12.38-rt53-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Yadi.hu"
Probably happens on all ARM, with
CONFIG_PREEMPT_RT_FULL
CONFIG_DEBUG_ATOMIC_SLEEP
This simple program
int main() {
*((char*)0xc0001000) = 0;
};
[ 512.742724] BU
On Fri, Mar 13, 2015 at 05:49:13AM +0100, Mike Galbraith wrote:
> On Thu, 2015-03-12 at 15:13 -0400, Steven Rostedt wrote:
> > Dear RT Folks,
> >
> > This is the RT stable review cycle of patch 3.14.34-rt32-rc1.
> >
> > Please scream at me if I messed something up.
>
> Hm, in both 12/14 series,
Added a new compatible string "ti,am437x-ocp2scp" for OCP2SCP module.
This is needed since except for the OCP2SCP used in AM437x, SYNC2 value
in OCP2SCP TIMING should be changed whereas the default value is sufficient
in AM437x.
Cc: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I
---
.../de
As per the TRMs of AM572x, OMAP4430, OMAP4460, OMAP543x, the value of
SYNC2 must be set to 0x6 in order to ensure correct operation.
So modified the SYNC2 value of OCP2SCP TIMING register to 0x6 in all the
platforms that use OCP2SCP driver except AM437x. Also introduced a new
compatible property s
On 03/13, Sergio Durigan Junior wrote:
>
> On Thursday, March 12 2015, Oleg Nesterov wrote:
>
> > And it seems that we all agree that the kernel should not dump this vma
> > too. Could you confirm that this is fine from gdb pov just in case?
>
> Yes, this is what we expect from the GDB side. This
On Wed, Mar 11, 2015 at 03:12:25PM +0100, Lukáš Czerner wrote:
>
> I though you were advocating for a solution independent on the file
> system. This is ext4 only solution, but I do not really have
> anything against this.
It would be nice if we could have a fs-independent solution so that we
don
On Thu, Mar 12, 2015 at 01:56:00PM -0300, Marcos Dione wrote:
> On Thu, Mar 12, 2015 at 11:35:13AM -0400, Michal Hocko wrote:
> > > > On Wed 11-03-15 19:10:44, Marcos Dione wrote:
> I think that what I'm trying to do is figure out what each value
> represents and where it's incuded, as if to ma
On 03/13, Borislav Petkov wrote:
>
> On Wed, Mar 11, 2015 at 06:35:07PM +0100, Oleg Nesterov wrote:
> > drop_init_fpu() makes no sense. We need drop_fpu() and only if
>
> Oh, please explain why. I can try to rhyme it up as something like "we
> don't need to restore FPU context when flushing the thr
On 13/03/2015 15:46, Jason Baron wrote:
> > The throttling algorithm computes a duration for the next IO, which is used
> > to
> > arm a timer in order to delay the request a bit. As timers are always
> > rounded
> > *UP* to the effective granularity, the timeout being 1ms in epoll_pwait is
>
mem_cgroup_lookup is a wrapper around mem_cgroup_from_id, which checks
that id != 0 before issuing the function call. Today, there is no point
in this additional check apart from optimization, because there is no
css with id <= 0, so that css_from_id, called by mem_cgroup_from_id,
will return NULL
On Fri, Mar 13, 2015 at 02:19:26PM +, Russell King - ARM Linux wrote:
> On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote:
> > Variable 'gephy' is assigned a value that is never used.
> >
> > Signed-off-by :
> > ---
> > arch/arm/mach-dove/common.c | 2 +-
> > 1 file changed, 1 insert
bitwise AND ("&") was used
in logical expressions with operands having "bool" type. Replaced
bitwise AND operators with logical AND.
Signed-off-by : Ameen Ali http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Le 12/03/2015 15:54, Alexandre Belloni a écrit :
> Use the soc detection infrastructure for sama5 initialization.
>
> Signed-off-by: Alexandre Belloni
> ---
> arch/arm/mach-at91/sama5.c | 49
> --
> arch/arm/mach-at91/soc.h | 13
> 2 fi
Hi Daniel,
> On Fri, Feb 20, 2015 at 3:42 PM, Beeresh Gopal
> wrote:
>> +/* Samsung framebuffer modifiers */
>> +
>> +/*
>> + * NV12 64x32 Tiled
>> + *
>> + * 2 planes Y and CbCr, grouped into 64x32 macro tiles,
>> + * with a non-standard order in memory (Z-shape).
>> + *
>> + * Pixel layout iden
On 03/13/2015 10:25 AM, Vaibhav Shinde wrote:
>
> On low memory situation, I see various shrinkers being invoked, but in
> lowmem_shrink() case, kswapd is found to be hogging for around 150msecs.
>
> Due to this my application suffer latency issue, as the cpu was not
> released by kswapd0.
>
> I
On Wed, Mar 11, 2015 at 12:39:36PM +, Hanjun Guo wrote:
[...]
> +static void __init psci_0_2_set_functions(void)
> +{
> + pr_info("Using standard PSCI v0.2 function IDs\n");
> + psci_function_id[PSCI_FN_CPU_SUSPEND] = PSCI_0_2_FN64_CPU_SUSPEND;
> + psci_ops.cpu_suspend = psci_cpu_
As Chris Ball has moved on to other assignments, he's no longer able to
help me maintain MMC. Let's remove him from the MMC sections in
MAINTAINERS and add him to CREDIT file.
This also affects the SDHCI DRIVER section, since its state now becomes
orphan.
Cc: Chris Ball
Signed-off-by: Ulf Hansso
On Fri, Mar 13, 2015 at 6:31 AM, Liviu Dudau wrote:
> On Thu, Mar 12, 2015 at 04:23:06PM -0500, Bjorn Helgaas wrote:
>> On Mon, Mar 09, 2015 at 10:33:57AM +0800, Yijing Wang wrote:
>> > ...
>> > Yijing Wang (29):
>> > PCI: Rip out pci_bus_add_devices() from pci_scan_bus()
>> > PCI: Rip out pci
401 - 500 of 843 matches
Mail list logo
