--
From: "Krzysztof Kozlowski"
Sent: Monday, June 08, 2015 7:40 AM
To: "Anand Moon" ; "Rob Herring"
; "Pawel Moll" ; "Mark Rutland"
; "Ian Campbell" ;
"Kumar Gala" ; "Kukjin Kim" ; "Alan
Stern" ; "Greg Kroah-Hartman"
; "Vivek Gautam" ;
(updated with one more patch)
Hello,
Contains two driver fixes. One is for ahci_mvebu controller config
bug and the other fixes pata_octeon_cf build issue.
Thanks.
The following changes since commit dbfe8ef5599a5370abc441fcdbb382b656563eb4:
ahci: avoton port-disable reset-quirk (2015-05-10
Hi,
On Monday, June 08, 2015 10:44 AM, "Krzysztof Kozlowski"
wrote:
my apologies for being late in replying to this thread.
2015-06-08 13:21 GMT+09:00 Anand Moon :
Hi Krzysztof ,
On 8 June 2015 at 07:40, Krzysztof Kozlowski
wrote:
On 07.06.2015 22:20, Anand Moon wrote:
Facilitate
* Alexander Holler wrote:
> Am 08.06.2015 um 10:08 schrieb Richard Weinberger:
> >On Mon, Jun 8, 2015 at 9:40 AM, Alexander Holler
> >wrote:
> >>Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
> >>>
> >>>
> >>>* Linus Torvalds wrote:
> >>>
> Stop with the random BUG_ON() additions.
> >>>
>
Ping on this.
On Fri, May 08, 2015 at 02:31:30PM +0300, Mika Westerberg wrote:
> Using -1 as platform device id means that the platform driver core will not
> assign any id to the device (the device name will not have id at all). This
> results problems on systems that have multiple PCHs
This is necessary for making async cfq_cgroups per-cfq_group instead
of per-cfq_data. While this change makes cfq_get_queue() perform RCU
locking and look up cfq_group even when it reuses async queue, the
extra overhead is extremely unlikely to be noticeable given that this
is already sitting
On Mon, Jun 08, 2015 at 02:44:41PM +0800, Zhu Guihua wrote:
> When hot add two nodes continuously, we found the vmemmap region info is a
> bit messed. The last region of node 2 is printed when node 3 hot added,
> like the following:
> Initmem setup node 2 [mem
Async cfqq's (cfq_queue's) are shared across cfq_data. When
cfq_get_queue() obtains a new queue from cfq_find_alloc_queue(), it
stashes the pointer in cfq_data and reuses it from then on; however,
the function doesn't consider that cfq_find_alloc_queue() may return
the oom_cfqq under memory
Up until now, all async IOs were queued to async queues which are
shared across the whole request_queue, which means that blkcg resource
control is completely void on async IOs including all writeback IOs.
It was done this way because writeback didn't support writeback and
there was no way of
cfq_get_queue()'s control flow looks like the following.
async_cfqq = NULL;
cfqq = NULL;
if (!is_sync) {
...
async_cfqq = ...;
cfqq = *async_cfqq;
}
if (!cfqq)
cfqq = ...;
if
* Some were accessing cic->cfqq[] directly. Always use cic_to_cfqq()
and cic_set_cfqq().
* check_ioprio_changed() doesn't need to verify cfq_get_queue()'s
return for NULL. It's always non-NULL. Simplify accordingly.
This patch doesn't cause any functional changes.
Signed-off-by: Tejun
If the cfq_queue cached in cfq_io_cq is the oom one, cfq_set_request()
replaces it by invoking cfq_get_queue() again without putting the oom
queue leaking the reference it was holding. While oom queues are not
released through reference counting, they're still reference counted
and this can
Even when allocations fail, cfq_find_alloc_queue() always returns a
valid cfq_queue by falling back to the oom cfq_queue. As such, there
isn't much point in taking @gfp_mask and trying "harder" if __GFP_WAIT
is set. GFP_ATOMIC allocations don't fail often and even when they do
the degraded
cfq_find_alloc_queue() checks whether a queue actually needs to be
allocated, which is unnecessary as its sole caller, cfq_get_queue(),
only calls it if so. Also, the oom queue fallback logic is scattered
between cfq_get_queue() and cfq_find_alloc_queue(). There really
isn't much going on in the
Hello,
cfq has always charged all async IOs to the root cgroup. It didn't
have much choice as writeback didn't know about cgroups and there was
no way to tell who to blame for a given writeback IO. writeback
finally grew support for cgroups and now tags each writeback IO with
the appropriate
On Mon, Jun 08, 2015 at 10:34:58AM +0200, Ingo Molnar wrote:
> Rename the following system call entry points:
>
> ia32_cstar_target -> entry_SYSCALL_compat
> ia32_syscall-> entry_INT80_compat
>
> The generic naming scheme for x86 system call entry points is:
>
>
Hi Boris,
On 05/06/15 12:39, Boris Brezillon wrote:
> Hi Jon,
>
> On Fri, 5 Jun 2015 09:46:09 +0100
> Jon Hunter wrote:
>
>>
>> On 05/06/15 00:02, Paul Walmsley wrote:
>>> Hi folks
>>>
>>> just a brief comment on this one:
>>>
>>> On Thu, 30 Apr 2015, Boris Brezillon wrote:
>>>
Clock
Hello Pantelis
On Mon, Jun 8, 2015 at 10:14 AM, Pantelis Antoniou
wrote:
>>
>
> Either patch fixes (or rather papers over) the problem.
>
> The way I understand it is that we have two issues.
>
> 1. The rather obvious crash on device removal.
> 2. The of_platform_populate (and the subsequent
Am 08.06.2015 um 10:08 schrieb Richard Weinberger:
On Mon, Jun 8, 2015 at 9:40 AM, Alexander Holler wrote:
Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
* Linus Torvalds wrote:
Stop with the random BUG_ON() additions.
Yeah, so I propose the attached patch which attempts to resist new
Thanks. These look nice.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> From: Julia Lawall
>
> Delete jump to a label on the next line, when that label is not
> used elsewhere.
>
> A simplified version of the semantic patch that makes this change is as
> follows: (http://coccinelle.lip6.fr/)
>
> //
> @r@
> identifier l;
> @@
>
> -if (...) goto l;
> -l:
> //
The 'system_call' entry points differ starkly between native 32-bit and 64-bit
kernels: on 32-bit kernels it defines the INT 0x80 entry point, while on
64-bit it's the SYSCALL entry point.
This is pretty confusing when looking at generic code, and it also obscures
the nature of the entry point at
So the SYSENTER instruction is pretty quirky and it has different behavior
depending on bitness and CPU maker.
Yet we create a false sense of coherency by naming it 'ia32_sysenter_target'
in both of the cases.
Split the name into its two uses:
ia32_sysenter_target (32)->
This series does the following renames:
system_call (32) -> entry_INT80_32
system_call (64) -> entry_SYSCALL_64
ia32_cstar_target-> entry_SYSCALL_compat
ia32_syscall -> entry_INT80_compat
Rename the following system call entry points:
ia32_cstar_target -> entry_SYSCALL_compat
ia32_syscall-> entry_INT80_compat
The generic naming scheme for x86 system call entry points is:
entry_MNEMONIC_qualifier
where 'qualifier' is one of _32, _64 or
Make the 32-bit syscall entry code a bit more readable:
- use consistent assembly coding style similar to entry_64.S
- remove old comments that are not true anymore
- eliminate whitespace noise
- use consistent vertical spacing
- fix various comments
No code changed:
#
Rework slave configuration part in order to more report wrong errors
about the configuration.
Only maxburst and addr width values are checked when doing the slave
configuration. The validity of the channel configuration is done at
prepare time.
Signed-off-by: Ludovic Desroches
Cc:
Fix indentation.
Signed-off-by: Ludovic Desroches
---
drivers/dma/at_xdmac.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/dma/at_xdmac.c b/drivers/dma/at_xdmac.c
index e5dd730..7614c5c 100644
--- a/drivers/dma/at_xdmac.c
+++ b/drivers/dma/at_xdmac.c
MODULE_DEVICE_TABLE is referring to wrong driver's table and breaks the
build. Fix that.
Cc: sta...@vger.kernel.org
Signed-off-by: Aaro Koskinen
---
drivers/ata/pata_octeon_cf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ata/pata_octeon_cf.c
Hi stable folk,
On 08/05/15 15:16, James Hogan wrote:
> On 07/05/15 13:47, Nicholas Mc Guire wrote:
>> Fix possible unintended sign extension in unsigned MMIO loads by casting
>> to uint16_t in the case of mmio_needed != 2.
>>
>> Signed-off-by: Nicholas Mc Guire
>
> Looks good to me. I wrote an
On Mon, Jun 08, 2015 at 12:37:00PM +0530, Sumit Semwal wrote:
> H Peter, Felipe,
>
> On 14 January 2015 at 06:56, Peter Chen wrote:
> > On Tue, Jan 13, 2015 at 10:18:02AM -0600, Felipe Balbi wrote:
> >> On Tue, Jan 13, 2015 at 04:02:20PM +0530, Kiran Raparthy wrote:
> >> > Hi Felipe,
> >> >
> >>
Using _bh variant for spin locks causes this kind of warning:
Starting logging: [ cut here ]
WARNING: CPU: 0 PID: 3 at /ssd_drive/linux/kernel/softirq.c:151
__local_bh_enable_ip+0xe8/0xf4()
Modules linked in:
CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.1.0-rc2+ #94
Hi Viresh,
> On 25-05-15, 07:39, Shailendra Verma wrote:
> > During probe free the memory allocated to "exynos_info" in case of
> > unknown SOC type.
> >
> > Signed-off-by: Shailendra Verma
> > ---
> > drivers/cpufreq/exynos-cpufreq.c |6 --
> > 1 file changed, 4 insertions(+), 2
On Mon, 2015-06-08 at 11:06 +0300, Ander Conselvan De Oliveira wrote:
> On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-06-07, Ville Syrjälä wrote:
> > > On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > > > Hi
> > > >
> > > >
My pleasure, thanks.
Zhenhua
On 06/08/2015 04:23 PM, Joerg Roedel wrote:
On Mon, Jun 08, 2015 at 04:06:45PM +0800, Li, ZhenHua wrote:
Finished testing on my HP huge system, SuperDome X.
It works well.
Thanks for testing this, Zhen-Hua. Might I add your Tested-by to the
patches?
In the commit below, I missed the connector allocation in the function
intel_sdvo_analog_init(), leading to those connectors to have a NULL
state pointer.
commit 08d9bc920d465d762cac9383249c19bf69a2
Author: Ander Conselvan de Oliveira
Date: Fri Apr 10 10:59:10 2015 +0300
drm/i915:
On Mon, Jun 08, 2015 at 04:06:45PM +0800, Li, ZhenHua wrote:
> Finished testing on my HP huge system, SuperDome X.
> It works well.
Thanks for testing this, Zhen-Hua. Might I add your Tested-by to the
patches?
Joerg
--
To unsubscribe from this list: send the line "unsubscribe
Hi Vinod,
I have updated patch 1 as you requested.
About patch 2, I don't really find how to split it. I have applied it on 4.0.4
without any conflicts so backport will not be an issue.
Changes from v1:
- remove indentation fixes from patch for stable and put it in another one.
Ludovic
On Sat 06-06-15 15:51:35, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > > > Let's move check_panic_on_oom up before the current task is
> > > > checked so that the knob value is . Do the same for the memcg in
> > > > mem_cgroup_out_of_memory.
> > > >
> > > > Reported-by: Tetsuo Handa
> > > >
(CCed to linux-ni...@vger.kernel.org)
Hi Heinz,
On 2015/06/08 15:43, Heinz Diehl wrote:
Hi,
a nilfs2 formatted disk fails to mount via fstab due to double uuid's.
See lsblk output below. The logs indicate that the system attempts to
mount /dev/sdb rather than /dev/sdb1, which of course fails.
On Sat 06-06-15 11:54:32, Piotr Kwapulinski wrote:
> The simple check for zero length memory mapping may be performed
> earlier. It causes that in case of zero length memory mapping some
> unnecessary code is not executed at all. It does not make the code less
> readable and saves some CPU cycles.
On 6 June 2015 at 23:15, Robert Jarzmik wrote:
> From: Daniel Mack
>
> Switch over pxamci to dmaengine. This prepares the devicetree full
> support of pxamci.
>
> This was successfully tested on a PXA3xx board, as well as PXA27x.
>
> Signed-off-by: Daniel Mack
> [adapted to pxa-dma]
>
Hi Ricardo, Grant,
> On Jun 7, 2015, at 21:13 , Ricardo Ribalda Delgado
> wrote:
>
> Hello Grant
>
> I would ask you to go through all the discussion related to this bug.
> Here is a summary (please anyone involved correct me if I am wrong)
>
> 1) I send a patch to fix the oops if release
Within runnable tasks in /proc/sched_debug, vruntime is printed twice,
once as tree-key and again as exec-runtime.
Since exec-runtime isnt populated in !CONFIG_SCHEDSTATS, use this field
to print wait_sum.
Signed-off-by: Srikar Dronamraju
---
kernel/sched/debug.c | 4 ++--
1 file changed, 2
Current /proc/sched_debug can be improved by
- Improving the format of runnable tasks when CONFIG_SCHEDSTATS is not enabled.
- Adding sum_exec info even when CONFIG_SCHEDSTATS is not enabled.
- Removing duplicate information from runnable tasks.
- Adding wait-time info.
Further we could collect
Commit-ID: febe06962ab191db50e633a0f79d9fb89a2d1078
Gitweb: http://git.kernel.org/tip/febe06962ab191db50e633a0f79d9fb89a2d1078
Author: Axel Lin
AuthorDate: Sun, 7 Jun 2015 21:33:29 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 8 Jun 2015 10:08:50 +0200
irqchip: sunxi-nmi: Fix
Hello Thierry,
Am 05.06.2015 14:19, schrieb Thierry Reding:
On Wed, May 06, 2015 at 09:49:33AM +0200, Heiko Schocher wrote:
The patch adds LG4573 parallel RGB panel driver with SPI control interface.
The driver uses drm_panel framework.
This should be obvious by the location of the driver.
When CONFIG_SCHEDSTATS is enabled, /proc//sched prints almost all
sched statistics except sum_sleep_runtime. Since sum_sleep_runtime is
a good info to collect, add this it to /proc//sched.
Signed-off-by: Srikar Dronamraju
---
kernel/sched/debug.c | 1 +
1 file changed, 1 insertion(+)
diff
Hello Alexandre,
On Mon, Jun 8, 2015 at 9:41 AM, Alexandre Courbot wrote:
> The wifi chip on roth needs to have its reset deasserted in order to be
> probed. Add a mmc-pwrseq-simple to allow this to happen and get wifi
> working at boot time.
>
> Signed-off-by: Alexandre Courbot
> ---
>
With !CONFIG_SCHEDSTATS, runnable tasks in /proc/sched_debug has too
many columns than required. Fix this by printing appropriate columns.
While at this, print sum_exec_runtime, since this information is
available even in !CONFIG_SCHEDSTATS case.
Signed-off-by: Srikar Dronamraju
---
On Sun, Jun 7, 2015 at 3:33 PM, Axel Lin wrote:
> Signed-off-by: Axel Lin
> ---
> drivers/irqchip/irq-sunxi-nmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-sunxi-nmi.c b/drivers/irqchip/irq-sunxi-nmi.c
> index 12f547a..eb9b59e 100644
> ---
* Peter Zijlstra [2015-06-08 09:06:40]:
> On Thu, May 28, 2015 at 03:56:16PM +0530, Srikar Dronamraju wrote:
> >
> > Srikar Dronamraju (3):
> > sched:Properly format runnable tasks in /proc/sched_debug
> > sched:Replace vruntime with wait_sum in /proc/sched_debug
> > sched:Add
* Alexander Holler wrote:
> Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
> >
> >* Linus Torvalds wrote:
> >
> >>Stop with the random BUG_ON() additions.
> >
> > Yeah, so I propose the attached patch which attempts to resist new BUG_ON()
> > additions.
>
> As this reminded me at flame I
Finished testing on my HP huge system, SuperDome X.
It works well.
Thanks
Zhenhua
On 06/05/2015 10:10 PM, Joerg Roedel wrote:
Hey,
here are a couple of patches to fix the fall-out from the
patch set fixing the kdump faults with VT-d enabled. A few
important issues have been fixed:
*
On Mon, Jun 8, 2015 at 9:40 AM, Alexander Holler wrote:
> Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
>>
>>
>> * Linus Torvalds wrote:
>>
>>> Stop with the random BUG_ON() additions.
>>
>>
>> Yeah, so I propose the attached patch which attempts to resist new
>> BUG_ON()
>> additions.
>
>
> As
On Sun, 2015-06-07 at 04:32 +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-06-07, Ville Syrjälä wrote:
> > On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > > Hi
> > >
> > > On 2015-04-20, Dave Airlie wrote:
> > > [...]
> > > > The following changes since
On Mon, 8 Jun 2015, Oleg Nesterov wrote:
> On 06/08, Oleg Nesterov wrote:
> >
> > And I simply can not understand the complication in hrtimer_active(),
> > please help!
>
> Sorry for another off-topic email, but I don't even understand the
> usage of hrtimer_active().
>
> Say, do_nanosleep()
>
Hi Paul,
On 06/06/2015 02:57 PM, Paul Bolle wrote:
> On Fri, 2015-06-05 at 17:06 +0200, Eric Auger wrote:
>> --- /dev/null
>> +++ b/drivers/vfio/platform/reset/vfio_platform_calxedaxgmac.c
>
>> +static int __init vfio_platform_calxedaxgmac_init(void)
>> +{
>> +return 0;
>> +}
>> +
>> +static
On Sun, Jun 07, 2015 at 09:33:29PM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin
Acked-by: Maxime Ripard
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
signature.asc
Description: Digital signature
Commit-ID: 55963c9f20d03124eefb4c365e1ca1f485fc3974
Gitweb: http://git.kernel.org/tip/55963c9f20d03124eefb4c365e1ca1f485fc3974
Author: Sudeep Holla
AuthorDate: Fri, 5 Jun 2015 11:59:57 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 5 Jun 2015 22:26:33 +0200
irqchip: gic: Simplify
Commit-ID: 496c28b13eb9d4f9c751b672daad8b110084cfd8
Gitweb: http://git.kernel.org/tip/496c28b13eb9d4f9c751b672daad8b110084cfd8
Author: Geert Uytterhoeven
AuthorDate: Fri, 29 May 2015 11:27:43 +0200
Committer: Thomas Gleixner
CommitDate: Fri, 5 Jun 2015 22:26:33 +0200
irqchip: renesas:
On Jun 8, 2015, at 3:24 AM, Julia Lawall wrote:
>> You are right, set_pga seems to be a dead member. It was alive a once, but
>> somehow not fully removed now,
>> so it's safe to drop the whole if and also the struct member itself.
>> set_oabufs could be dropped as well.
>
> Looking
在 2015年06月08日 15:11, Caesar Wang 写道:
We need different orderings when turning a core on and turning a core
off. In one case we need to assert reset before turning power off.
In ther other case we need to turn power on and the deassert reset.
In general, the correct flow is:
CPU off:
From: Jaeden Amero
Date: Fri, 5 Jun 2015 18:00:23 -0500
> In v2, we add an additional cleanup commit to make an array of strings
> static const and to improve const correctness generally. We also no longer
> unnecessarily initialize the result variable in
> ksz9031_center_flp_timing().
>
> In
Hi Rob, Scott,
On 06/05/2015 11:14 PM, Scott Wood wrote:
> On Fri, 2015-06-05 at 13:05 -0500, Rob Herring wrote:
>> On Fri, Jun 5, 2015 at 10:06 AM, Eric Auger
>> wrote:
>>> In situations where the userspace driver is stopped abnormally and
>>> the
>>> VFIO platform device is released, the
From: Borislav Petkov
Hi,
I've already sent you the bigger part last week, thinking that the merge
window is getting close but it looks like we'll have an rc8 and then
some. Nice.
Anyway, here's Joerg's stuff which has been running in our SLES kernels
without an issue for a while now.
Joerg
From: Joerg Roedel
Print a warning when all allocation tries have been failed
and the function is about to return NULL. This prepares for
calling the function with __GFP_NOWARN to suppress
allocation failure warnings before all fall-backs have
failed.
Signed-off-by: Joerg Roedel
Acked-by:
From: Joerg Roedel
When the crash kernel is loaded above 4GiB in memory, the
first kernel allocates only 72MiB of low-memory for the DMA
requirements of the second kernel. On systems with many
devices this is not enough and causes device driver
initialization errors and failed crash dumps.
From: Joerg Roedel
When we boot a kdump kernel in high memory, there is by
default only 72MB of low memory available. The swiotlb code
takes 64MB of it (by default) so that there are only 8MB
left to allocate from. On systems with many devices this
causes page allocator warnings from
On Fri, Jun 5, 2015 at 10:12 PM, Fabian Frederick wrote:
> ceph used -1 for the last match_table_t option.
> Use Opt_err enum like other FS
>
> match_token() is based on the pattern (NULL)
> so behavior should remain the same.
>
> Signed-off-by: Fabian Frederick
> ---
> This is untested. If this
On Fri, Jun 05, 2015 at 05:59:12PM -0700, Stephen Boyd wrote:
> On 06/05, James Liao wrote:
> > Hi Stephen,
> >
> > On Thu, 2015-06-04 at 14:02 -0700, Stephen Boyd wrote:
> > > On 05/29, Sascha Hauer wrote:
> > > > Yes. I previously got the impression that the subsystem clocks are not
> > > >
Fix a memory leak by freeing the memory allocated in kobject_set_name
for the kobjet name.
unreferenced object 0xe2167700 (size 64):
comm "swapper/0", pid 1, jiffies 4294938161 (age 90.540s)
hex dump (first 32 bytes):
6d 61 67 6e 65 74 69 63 00 11 c2 c0 1f e9 23 c1 magnetic..#.
On Fri, 5 Jun 2015, John Stultz wrote:
> On Fri, Jun 5, 2015 at 3:07 AM, Ingo Molnar wrote:
> > * Thomas Gleixner wrote:
> >> It's not about copying 24 bytes. It's about touching 3 cache lines for
> >> nothing.
> >> In situations where we run high frequency periodic timers on clock
> >>
The wifi chip on roth needs to have its reset deasserted in order to be
probed. Add a mmc-pwrseq-simple to allow this to happen and get wifi
working at boot time.
Signed-off-by: Alexandre Courbot
---
arch/arm/boot/dts/tegra114-roth.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git
Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
* Linus Torvalds wrote:
Stop with the random BUG_ON() additions.
Yeah, so I propose the attached patch which attempts to resist new BUG_ON()
additions.
As this reminded me at flame I received once from a maintainer because I
wanted to avoid a
On Sunday 07 June 2015 21:12:38 Darren Hart wrote:
> On Sat, Jun 06, 2015 at 10:23:27AM +0200, Pali Rohár wrote:
> > This patch series add new acpi Dell Airplane Mode Switch driver (DELLABCE
> > and
> > DELRBTN acpi devices). It provides radio HW switch events (together with
> > current
> >
Hi Stephen,
On Fri, 2015-06-05 at 17:59 -0700, Stephen Boyd wrote:
> Perhaps an example would be best. In DT we would have:
>
> vencsys: vencsys@1 {
> compatible = "mtk,vencsys";
> reg = <0x1 0x1000>;
> #clock-cells = <1>;
>
Hi Eddie,
On Mon, Jun 01, 2015 at 09:08:27PM +0800, Eddie Huang wrote:
> Add MT8173 I2C device nodes, include I2C controllers and pins.
> MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
> The 6th I2C controller register base doesn't next to 5th I2C,
> and there is a hardware
Hello,
On 06/08/2015 12:11 PM, Uwe Kleine-König wrote:
Hello,
On Mon, Jun 01, 2015 at 10:51:06AM +0530, Bhuvanchandra DV wrote:
The LPUART does not provide manual control of RTS/CTS signals,
those can only be controlled by the hardware directly. Therefore
manual control of those signals
> You are right, set_pga seems to be a dead member. It was alive a once, but
> somehow not fully removed now,
> so it's safe to drop the whole if and also the struct member itself.
> set_oabufs could be dropped as well.
Looking further, in the same function I also don't see any other uses
On Fri, Jun 05, 2015 at 04:10:19PM +0200, Guenter Roeck wrote:
> The newly wired system calls cause compile errors when building
> crisv10 images.
>
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x580): undefined reference to `_sys_sched_setattr'
>
On Tue, May 26, 2015 at 11:06:34PM +0200, Robert Jarzmik wrote:
> Add documentation about acking the transfers, and their
> reusability.
>
> Signed-off-by: Robert Jarzmik
> Cc: Maxime Ripard
Acked-by: Maxime Ripard
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and
Use the below scripts to check:
scripts/checkpatch.pl -f --subject arch/arm/mach-rockchip/platsmp.c
Signed-off-by: Caesar Wang
Changes in v5:
- Add the changelog.
Changes in v4: None
Changes in v3: None
Changes in v2:
- Use the checkpatch.pl -f --subjective to check.
---
The patch can ensure that v7_exit_coherency_flush() in rockchip_cpu_die()
executed in time.
The mdelay(1) has enough time to fix the problem of CPU offlining.
That's a workaround way in rockchip hotplug code,
At least, we haven't a better way to solve it. Who know,
that maybe fixed by chip
* Linus Torvalds wrote:
> Stop with the random BUG_ON() additions.
Yeah, so I propose the attached patch which attempts to resist new BUG_ON()
additions.
Thanks,
Ingo
>
>From 724052923fbae2e3a14e0b9383c89b18217d817f Mon Sep 17 00:00:00 2001
From:
We need different orderings when turning a core on and turning a core
off. In one case we need to assert reset before turning power off.
In ther other case we need to turn power on and the deassert reset.
In general, the correct flow is:
CPU off:
reset_control_assert
Verified on url =
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14
Tested by 176000 cycles are pass with CPU up/dowm test scripts.
Caesar Wang (3):
ARM: rockchip: fix the CPU soft reset
ARM: rockchip: ensure CPU to enter WFI/WFE state
ARM: rockchip: fix
H Peter, Felipe,
On 14 January 2015 at 06:56, Peter Chen wrote:
> On Tue, Jan 13, 2015 at 10:18:02AM -0600, Felipe Balbi wrote:
>> On Tue, Jan 13, 2015 at 04:02:20PM +0530, Kiran Raparthy wrote:
>> > Hi Felipe,
>> >
>> > On 1 December 2014 at 11:09, Kiran Raparthy wrote:
>> > > Hi Felipe,
>> >
On Thu, May 28, 2015 at 03:56:16PM +0530, Srikar Dronamraju wrote:
>
> Srikar Dronamraju (3):
> sched:Properly format runnable tasks in /proc/sched_debug
> sched:Replace vruntime with wait_sum in /proc/sched_debug
> sched:Add sum_sleep_runtime to /proc//sched
All patches are lacking a
Hello Krzysztof,
On Mon, Jun 8, 2015 at 8:52 AM, Krzysztof Kozlowski
wrote:
> 2015-06-08 15:42 GMT+09:00 Javier Martinez Canillas :
>> Hello,
>>
>> On Mon, Jun 8, 2015 at 7:14 AM, Krzysztof Kozlowski
>> wrote:
>>
>> [...]
>>
>>>
>>> To summarize my point of view:
>>> 1. Unless Vivek's says
Eduardo, Rui,
Any feedback to this series?
Thanks
Sascha
On Wed, May 20, 2015 at 03:20:30PM +0200, Sascha Hauer wrote:
> This series adds support for hardware trip points. It picks up earlier
> work from Mikko Perttunen. Mikko implemented hardware trip points as part
> of the device tree
On Fri, 2015-06-05 at 13:23 +, Mathieu Desnoyers wrote:
> sched_wakeup: when try_to_wake_up{,_local} is called in the waker.
> sched_activate_task: when the wakee is marked runnable.
> sched_switch: when scheduling actually happens.
>
> We can then calculate wakeup latency as
>
>
Hello Krzysztof,
On Mon, Jun 8, 2015 at 3:35 AM, Krzysztof Kozlowski
wrote:
> During probe the regulator (if present) was enabled but not disabled in
> case of failure. So an unsuccessful probe lead to enabling the
> regulator which was actually not needed because the device was not
> enabled.
>
2015-06-08 15:42 GMT+09:00 Javier Martinez Canillas :
> Hello,
>
> On Mon, Jun 8, 2015 at 7:14 AM, Krzysztof Kozlowski
> wrote:
>
> [...]
>
>>
>> To summarize my point of view:
>> 1. Unless Vivek's says otherwise, please give him the credits with
>> proper "from" field.
>> 2. Issues mentioned in
* Denys Vlasenko wrote:
> I broke this recently when I changed pt_regs->r8..r11 clearing logic
> in INT 80 code path.
>
> There is a branch from SYSENTER/SYSCALL code to INT 80 code:
> if we fail to retrieve arg6, we return EFAULT. Before this patch,
> in this case we don't clear
On 08.06.2015, Heinz Diehl wrote:
> [root@keera ~]# lsblk -f
> NAMEFSTYPE LABEL UUID MOUNTPOINT
> sdb ff17dda9-fcae-42e7-a438-9087de58902e
>
> `-sdb1 xfs
From: Nicholas Mc Guire
Date: Sun, 7 Jun 2015 12:35:46 +0200
> API compliance scanning with coccinelle flagged:
> ./drivers/net/wan/dscc4.c:1036:1-33:
> WARNING: timeout (10) seems HZ dependent
> ./drivers/net/wan/dscc4.c:554:2-34:
> WARNING: timeout (10) seems HZ dependent
>
From: Nicholas Mc Guire
Date: Sun, 7 Jun 2015 10:25:58 +0200
> for the dscc4 case Im not sure - that seems to have gone in in 2.4
> and that had HZ configurable. The cosa case was checked
> again 2.2.26 (no config HZ) and the timeout there was 30 -> 300ms.
>
> I think that this is consistent
When hot add two nodes continuously, we found the vmemmap region info is a
bit messed. The last region of node 2 is printed when node 3 hot added,
like the following:
Initmem setup node 2 [mem 0x-0x]
On node 2 totalpages: 0
Built 2 zonelists in Node order,
Hello,
On Mon, Jun 8, 2015 at 7:14 AM, Krzysztof Kozlowski
wrote:
[...]
>
> To summarize my point of view:
> 1. Unless Vivek's says otherwise, please give him the credits with
> proper "from" field.
> 2. Issues mentioned in previous mail should be addressed (missing
> IS_ERR(), how disabling
701 - 800 of 1618 matches
Mail list logo
