To guarantee a low latency also to the I/O requests issued by soft
real-time applications, this patch introduces a further heuristic,
which weight-raises (in the sense explained in patch 8) also the
queues associated to applications deemed as soft real-time.
To be deemed as soft real-time, an
This patch introduces a simple heuristic to load applications quickly,
and to perform the I/O requested by interactive applications just as
quickly. To this purpose, both a newly-created queue and a queue
associated with an interactive application (we explain in a moment how
BFQ decides whether
From: Fabio Checconi
Complete support for full hierarchical scheduling, with a cgroups
interface. The name of the new subsystem is bfqio.
Weights can be assigned explicitly to groups and processes through the
cgroups interface, differently from what happens, for single
processes, if the cgroups
The dgap_probe1() function is just calling dgap_found_board().
So it is removed and dgap_found_board() is called directly.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c
The feedback-loop algorithm used by BFQ to compute queue (process)
budgets is basically a set of three update rules, one for each of the
main reasons why a queue may be expired. If many processes suddenly
switch from sporadic I/O to greedy and sequential I/O, then these
rules are quite slow to
Adds a label for "kfree(brd)". And also remove
a state value as BOARD_FAILED in brd when dgap_do_remap() is failed.
Because "brd" will free after failure.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c | 19 ++-
1 files changed, 14 insertions(+), 5 deletions(-)
On Tue, May 27, 2014 at 11:18:15AM +0100, Harini Katakam wrote:
> Add cadence-wdt bindings documentation.
>
> Signed-off-by: Harini Katakam
> ---
>
> v2:
> No changes
>
> ---
> .../devicetree/bindings/watchdog/cadence-wdt.txt | 26
>
> 1 file changed, 26
(2014/05/29 16:27), Jon Maxwell wrote:
> There has been a number incidents recently where customers running KVM have
> reported that VM hosts on different Hypervisors are unreachable. Based on
> pcap traces we found that the bridge was broadcasting the ARP request out
> onto the network. However
On Thu, May 29, 2014 at 06:11:09PM +0900, Daeseok Youn wrote:
> Adds a label for "kfree(brd)". And also remove
> a state value as BOARD_FAILED in brd when dgap_do_remap() is failed.
> Because "brd" will free after failure.
Yes. Perfect. Eventually BOARD_FAILED will be removed completely.
On 05/29/2014 02:07 AM, Mike Turquette wrote:
> Quoting Sebastian Hesselbarth (2014-05-19 09:43:21)
>> Mike,
>>
>> this is v2 of the Berlin SoC clock driver [1] but with a reworked DT
>> binding as requested [2]. We decided to not even try to split up the chip
>> control registers that deal with
On Tue, May 27, 2014 at 11:18:14AM +0100, Harini Katakam wrote:
> Add Cadence WDT driver. This is used by Xilinx Zynq.
>
> Signed-off-by: Harini Katakam
> ---
>
> Sorry for the delay in sending v2.
> v2 changes:
> - Update IO helpers.
> - Use dev_dbg instead of dev_info where possible.
> - Use
Am 29.05.2014 11:07, schrieb Pavel Emelyanov:
> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
>> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
>>> On 05/28/2014 10:28 PM, Vasily Kulikov wrote:
On Wed, May 28, 2014 at 16:44 +0400, Pavel Emelyanov wrote:
It will be simplier
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt
This switches the SPEAr PLGPIO driver over to using the irqchip
helpers.
As part of this effort, also get rid of the strange irq_base
calculation and failure to use d->hwirq for obtaining a local
irqchip offset.
Cc: Viresh Kumar
Cc: Shiraz Hashim
Cc: spear-de...@list.st.com
Signed-off-by:
On Wednesday 28 May 2014 14:41:52 H. Peter Anvin wrote:
> On 05/19/2014 05:36 AM, Arnd Bergmann wrote:
> >
> > My feeling is that all devices we can think of fall into at least one
> > of these categories:
> >
> > * legacy PC stuff that needs only byte access
> > * PCI devices that can be
Hi Mark,
On Thu, May 29, 2014 at 2:42 PM, Mark Rutland wrote:
> On Tue, May 27, 2014 at 11:18:15AM +0100, Harini Katakam wrote:
>> Add cadence-wdt bindings documentation.
>>
>> Signed-off-by: Harini Katakam
>> ---
>>
>> v2:
>> No changes
>> +Optional properties
>> +- reset
This patch is basically the counterpart of patch 13 for NCQ-capable
rotational devices. Exactly as patch 13 does on flash-based devices
and for any workload, this patch disables device idling on rotational
devices, but only for random I/O. More precisely, idling is disabled
only for
This patch boosts the throughput on NCQ-capable flash-based devices,
while still preserving latency guarantees for interactive and soft
real-time applications. The throughput is boosted by just not idling
the device when the in-service queue remains empty, even if the queue
is sync and has a
From: Arianna Avanzini
A set of processes may happen to perform interleaved reads, i.e.,
read requests whose union would give rise to a sequential read pattern.
There are two typical cases: first, processes reading fixed-size chunks
of data at a fixed distance from each other; second, processes
On 05/27/2014 12:18 PM, Harini Katakam wrote:
> Add cadence-wdt bindings documentation.
>
> Signed-off-by: Harini Katakam
> ---
>
> v2:
> No changes
>
> ---
> .../devicetree/bindings/watchdog/cadence-wdt.txt | 26
>
> 1 file changed, 26 insertions(+)
> create mode
Hi Mark,
On Thu, May 29, 2014 at 2:51 PM, Mark Rutland wrote:
> On Tue, May 27, 2014 at 11:18:14AM +0100, Harini Katakam wrote:
>> Add Cadence WDT driver. This is used by Xilinx Zynq.
>>
>> Signed-off-by: Harini Katakam
>> ---
>>
>> Sorry for the delay in sending v2.
>> v2 changes:
>> - Update
On 05/29/2014 03:25 AM, Rik van Riel wrote:
On 05/28/2014 08:16 AM, Raghavendra K T wrote:
This patch looks very promising.
Thank you Rik.
[...]
- My kernbench/ebizzy test on baremetal (32 cpu +ht sandybridge) did not seem to
show the impact of extra cmpxchg. but there should be effect
On 05/29/2014 01:21 PM, Richard Weinberger wrote:
> Am 29.05.2014 11:07, schrieb Pavel Emelyanov:
>> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
>>> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
On 05/28/2014 10:28 PM, Vasily Kulikov wrote:
> On Wed, May 28, 2014 at 16:44
Hi Mark,
>> +static struct of_device_id cdns_wdt_of_match[] = {
>> + { .compatible = "xlnx,zynq-wdt-r1p2", },
>> + { .compatible = "cdns,wdt-r1p2", },
>
> If these can currently be handled identically, why not just have
> "cdns,wdt-r1p2" in the driver and in your dts have:
>
>
On 05/29/2014 12:16 PM, Peter Zijlstra wrote:
On Wed, May 28, 2014 at 05:46:39PM +0530, Raghavendra K T wrote:
In virtualized environment there are mainly three problems
related to spinlocks that affect performance.
1. LHP (lock holder preemption)
2. Lock Waiter Preemption (LWP)
3.
On Thu, May 29, 2014 at 09:07:05AM +0100, Will Deacon wrote:
> On Wed, May 28, 2014 at 09:19:55PM +0100, Mark Brown wrote:
> > On Wed, Apr 30, 2014 at 06:54:33PM +0900, AKASHI Takahiro wrote:
> > > +#include
> > > +#include
> > > +#include
> > asm/insn.h contains a bunch of C stuff which
On Fri, May 23, 2014 at 05:53:04PM +0200, Vincent Guittot wrote:
> If the CPU is used for handling lot of IRQs, trig a load balance to check if
> it's worth moving its tasks on another CPU that has more capacity
>
> Signed-off-by: Vincent Guittot
> ---
> kernel/sched/fair.c | 13 +
>
>From time to time users report that UML hangs and consumes 100% CPU
on the host side.
Analyzing such an issue uncovered a bug in UML's page fault
handler. If the kernel tries to access userspace memory without
copy_from/to_user() UML receives a SIGSEGV and tries to handle
it. As the page fault
There is no need to go through handle_page_fault().
If we try to access the zero page in kernel mode just panic().
Signed-off-by: Richard Weinberger
---
arch/um/kernel/trap.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch/um/kernel/trap.c
> -Original Message-
> From: containers-boun...@lists.linux-foundation.org
> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
> > On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
> >> On 05/28/2014 10:28 PM, Vasily Kulikov wrote:
> >>> On Wed, May 28, 2014 at 16:44 +0400, Pavel
Am 29.05.2014 11:41, schrieb Pavel Emelyanov:
> On 05/29/2014 01:21 PM, Richard Weinberger wrote:
>> Am 29.05.2014 11:07, schrieb Pavel Emelyanov:
>>> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
> On 05/28/2014 10:28 PM, Vasily
(2014/05/29 6:44), Arnaldo Carvalho de Melo wrote:
> Masami-san,
>
> While trying:
>
> [root@zoo ~]# perf probe 'vfs_getname=getname_flags:65
> pathname=result->name:string'
> Failed to find the location of result at this address.
> Perhaps, it has been optimized out.
> Failed to find
Hi all,
The powerpc allyesconfig is again broken more than usual.
Changes since 20140528:
The powerpc tree gained a conflict against Linus' tree.
The nfsd tree lost its build failure.
The vfs tree gained conflicts against Linus' and the nfs trees.
The driver-core tree lost its build failure.
On 05/29/2014 01:54 PM, Richard Weinberger wrote:
> Am 29.05.2014 11:41, schrieb Pavel Emelyanov:
>> On 05/29/2014 01:21 PM, Richard Weinberger wrote:
>>> Am 29.05.2014 11:07, schrieb Pavel Emelyanov:
On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
> On Wed, May 28, 2014 at 23:27 +0400,
After 07d410e0) serial: sirf: fix spinlock deadlock issue it is no longer
possiblet to compile this driver. The rename of one of the spinlocks is
faulty. After looking at the original patch I believe this is the correct
fix.
Compile tested using ARM's multi_v7_defconfig
Cc: Greg Kroah-Hartman
Marian Marinov writes:
> Hello,
>
> I have the following proposition.
>
> Number of currently running processes is accounted at the root user
> namespace. The problem I'm facing is that multiple
> containers in different user namespaces share the process counters.
That is deliberate.
> So if
After 07d410e0) serial: sirf: fix spinlock deadlock issue it is no longer
possiblet to compile this driver. The rename of one of the spinlocks is
faulty. After looking at the original patch I believe this is the correct
fix.
Compile tested using ARM's multi_v7_defconfig
Cc: Greg Kroah-Hartman
On Thu, May 29, 2014 at 10:23:01AM +0100, Lorenzo Pieralisi wrote:
> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
>
Ben, I am withdrawing this series as it will be superseeded by a new
version. You probably did not intend to merge it, but just in case. :)
On Mon, May 19, 2014 at 3:51 PM, Alexandre Courbot wrote:
> Fix a very shameful memory leak and a compilation error due to the use of
> non-exported CMA
Am 29.05.2014 12:02, schrieb Pavel Emelyanov:
>>> We need to know what pid namespaces a task lives in and how pid, sid and
>>> pgid look in all of them. A short example with pids only
>>
>> So use case is to checkpoint/restore nested containers? :)
>
> Yes, but there's one more scenario. AFAIK
On Thu, May 29, 2014 at 04:57:07PM +0800, Li Zefan wrote:
> I don't think Ralf has committed it, so we'll send out a fix
> with detailed changelog.
It's queued to go upstream, commit e5eb925a1804c4a52994ba57f4f68ee7a9132905.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe
Miklos Szeredi wrote:
> Perfect solution would be an invisible temp directory. This needs filesystem
> support, but perhaps not so difficult. Again could be done later without
> backward compatibility issues.
Maybe make a tempfile and hardlink it into place when complete. That's what
changes since v2:
1. removed unwanted label implementation.
When we use devm_* APIs ,probe() failed also the memory
will be freed automatically. Thanks to Alex
-Varka Bhadram
Signed-off-by: Varka Bhadram
---
drivers/net/ieee802154/mrf24j40.c | 30 --
1 file
On Thu, May 29, 2014 at 03:43:45AM -0400, Chen, Gong wrote:
> On Wed, May 28, 2014 at 12:56:25PM -0400, Steven Rostedt wrote:
> > My concern is passing in a large string and wasting a lot of the ring
> > buffer space. The max you can hold per event is just under a page size
> > (4k). And all these
On 05/29/2014 02:19 PM, Richard Weinberger wrote:
> Am 29.05.2014 12:02, schrieb Pavel Emelyanov:
We need to know what pid namespaces a task lives in and how pid, sid and
pgid look in all of them. A short example with pids only
>>>
>>> So use case is to checkpoint/restore nested
On Thu, May 29, 2014 at 04:41:17PM +0900, Minchan Kim wrote:
> Hello Rusty,
>
> On Thu, May 29, 2014 at 04:56:41PM +0930, Rusty Russell wrote:
> > They don't make much difference: the easier fix is use gcc 4.8
> > which drops stack required across virtio block's virtio_queue_rq
> > down to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2014 01:06 PM, Eric W. Biederman wrote:
> Marian Marinov writes:
>
>> Hello,
>>
>> I have the following proposition.
>>
>> Number of currently running processes is accounted at the root user
>> namespace. The problem I'm facing is that
On 05/29/2014 01:53 PM, chenhanx...@cn.fujitsu.com wrote:
>
>
>> -Original Message-
>> From: containers-boun...@lists.linux-foundation.org
>> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
>>> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
On 05/28/2014 10:28 PM, Vasily
Hi Varka,
On Thu, May 29, 2014 at 03:57:38PM +0530, Varka Bhadram wrote:
> changes since v2:
> 1. removed unwanted label implementation.
>
> When we use devm_* APIs ,probe() failed also the memory
> will be freed automatically. Thanks to Alex
>
> -Varka Bhadram
>
>
you should provide a
Fix a segfault bug by asking for variable it doesn't find.
Since the convert_variable() didn't handle error code returned
from convert_variable_location(), it just passed an incomplete
variable field and then a segfault was occured when formatting
the field.
This fixes that bug by handling
From: 'Arnaldo Carvalho de
...
> > > So, yes, the user _can_ process the packets already copied to userspace,
> > > i.e. no packet loss, and then, on the next call, will receive the signal
> > > notification.
>
> > The application shouldn't need to see an EINTR response, any signal handler
> >
When I run my unionmount testsuite against overlayfs, I get the following
lockdep warning (unionmount is not in the kernel sources in this test):
[ BUG: lock held when returning to user space! ]
3.15.0-rc6-fsdevel+ #363 Tainted: GW
On Thursday, May 29, 2014 10:41:43 AM Zdenek Kabelac wrote:
> Hi
>
>
> I've noticed this message in my dmesg:
> (Possibly related to this commit?:
> a8d22396302b7e4e5f0a594c1c1594388c29edaf)
Well, does reverting that commit make the warning go away?
Rafael
> (My vanilla git commit number for
Arnaldo, this fixes the SEGV bug which you reported.
But I've found that perf probe sometimes loses the location of variables
with recent DWARF implementation. I need to check and fix that too.
Anyway, this patch should be applied for fixing critical bug.
Thank you,
(2014/05/29 19:52), Masami
On Thu, May 29, 2014 at 01:51:07PM +0300, Mika Westerberg wrote:
> On Thu, May 29, 2014 at 06:34:44AM +0100, Al Viro wrote:
> > On Thu, May 29, 2014 at 04:52:33AM +0100, Al Viro wrote:
> > > On Thu, May 29, 2014 at 04:11:49AM +0100, Al Viro wrote:
> > > > On Wed, May 28, 2014 at 07:39:54PM +0100,
On Thu, May 29, 2014 at 04:56:43PM +0930, Rusty Russell wrote:
> This is the only place which doesn't hand virtqueue_add_inbuf or
> virtqueue_add_outbuf a well-formed, well-terminated sg. Fix it,
> so we can make virtio_add_* simpler.
>
> Signed-off-by: Rusty Russell
> ---
>
Minchan Kim writes:
> Hello Rusty,
>
> On Thu, May 29, 2014 at 04:56:41PM +0930, Rusty Russell wrote:
>> They don't make much difference: the easier fix is use gcc 4.8
>> which drops stack required across virtio block's virtio_queue_rq
>> down to that kmalloc in virtio_ring from 528 to 392 bytes.
Peter Zijlstra writes:
> On Thu, May 29, 2014 at 04:56:45PM +0930, Rusty Russell wrote:
>> Before:
>> gcc 4.8.2: virtio_blk: stack used = 392
>> gcc 4.6.4: virtio_blk: stack used = 480
>>
>> After:
>> gcc 4.8.2: virtio_blk: stack used = 408
>> gcc 4.6.4: virtio_blk: stack
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
> always-on
Dear Customer;
We are into sale-ling and buying Our company needs your products, can you
send us complete catalog?
Best regards,
Mrs umar
--
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
On Thu, May 29, 2014 at 13:07 +0400, Pavel Emelyanov wrote:
> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
> > On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
> > ] We need a direct method of getting the pid inside containers.
> > ] If some issues occurred inside container guest, host
Reformat the comment describing this comedi driver to use the usual
block comment format.
Also remove reference to digital I/O emulating an 8255, because it
doesn't, and remove "DIO only" from the "Description:" line as it also
supports analog inputs.
Signed-off-by: Ian Abbott
---
I received a patch from the original author of the driver, Fred Brooks,
to add support for switching the input range and the
single-ended/differential input mode for the AI subdevice.
I used the patch as-is apart from minor whitespace fixes and
reformatting the changes to the driver description
The first patch reformats (and slightly changes) the driver comment to
avoid checkpatch warnings for the second patch.
The second patch adds functionality to the AI subdevice and is the work
of the original author, Fred Brooks.
1) staging: comedi: ni_daq_700: update driver comment
2) staging:
David Howells wrote:
>
> [ BUG: lock held when returning to user space! ]
> 3.15.0-rc6-fsdevel+ #363 Tainted: GW
>
> mount/4183 is leaving the kernel with locks still held!
> 1 lock held
On Thu, May 29, 2014 at 04:56:44PM +0930, Rusty Russell wrote:
> We used to have several callers which just used arrays. They're
> gone, so we can use sg_next() everywhere, simplifying the code.
>
> Before:
> gcc 4.8.2: virtio_blk: stack used = 392
> gcc 4.6.4: virtio_blk: stack used
On Wed, May 28, 2014 at 04:47:24PM -0700, H. Peter Anvin wrote:
> On 05/27/2014 02:58 PM, Seth Forshee wrote:
> >
> > The patches implement a psuedo filesystem for loop devices, which will
> > allow use of loop devices in containters using standard utilities. Under
> > normal use a loopfs mount
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-3.15-rc8
to receive ACPI and power management fixes for v3.15-rc8 (if
you decide to do -rc8) or for the final v3.15 (otherwise) with
top-most commit 9b961aa99b8155ecc07dd727643ca97424544256
On Thu, May 29, 2014 at 12:26 PM, David Howells wrote:
> Miklos Szeredi wrote:
>
>> Perfect solution would be an invisible temp directory. This needs filesystem
>> support, but perhaps not so difficult. Again could be done later without
>> backward compatibility issues.
>
> Maybe make a
On Thu, May 29, 2014 at 04:56:45PM +0930, Rusty Russell wrote:
> virtqueue_add() populates the virtqueue descriptor table from the sgs
> given. If it uses an indirect descriptor table, then it puts a single
> descriptor in the descriptor table pointing to the kmalloc'ed indirect
> table where the
This sequence of commands produces both errors:
mount -t tmpfs lower_layer /lower
mount -t tmpfs upper_layer /upper
mkdir /upper/upper
mkdir /upper/work
mount -t overlayfs overlayfs /mnt
-olowerdir=/lower,upperdir=/upper/upper,workdir=/upper/work
# The lockdep error was reported in the
On 05/29/2014 03:12 PM, Vasily Kulikov wrote:
> On Thu, May 29, 2014 at 13:07 +0400, Pavel Emelyanov wrote:
>> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
>>> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
>>> ] We need a direct method of getting the pid inside containers.
>>> ] If
On Thu, May 29, 2014 at 08:35:58PM +0930, Rusty Russell wrote:
> Peter Zijlstra writes:
> > On Thu, May 29, 2014 at 04:56:45PM +0930, Rusty Russell wrote:
> >> Before:
> >>gcc 4.8.2: virtio_blk: stack used = 392
> >>gcc 4.6.4: virtio_blk: stack used = 480
> >>
> >> After:
> >>gcc
> This patch provides the common I2C driver code for Intel SoC PMICs.
>
> Signed-off-by: Yang, Bin
> Signed-off-by: Zhu, Lejun
> ---
> v2:
> - Use regmap instead of creating our own I2C read/write callbacks.
> - Add one missing EXPORT_SYMBOL.
> - Remove duplicate code and put them into
> This patch adds Intel SoC PMIC support to the build files.
>
> Signed-off-by: Yang, Bin
> Signed-off-by: Zhu, Lejun
> ---
> v2:
> - Add select REGMAP_I2C.
> v3:
> - Add select REGMAP_IRQ.
> v4:
> - No change.
> ---
> drivers/mfd/Kconfig | 12
> drivers/mfd/Makefile | 3 +++
>
module_i2c_driver simplifies the code by eliminating
boilerplate code.
Signed-off-by: Sachin Kamat
---
drivers/mfd/menelaus.c | 23 +--
1 file changed, 1 insertion(+), 22 deletions(-)
diff --git a/drivers/mfd/menelaus.c b/drivers/mfd/menelaus.c
index
On Thu, 29 May 2014, Zhu, Lejun wrote:
> This patch provides chip-specific support for Crystal Cove. Crystal
> Cove is the PMIC in Baytrail-T platform.
>
> Signed-off-by: Yang, Bin
> Signed-off-by: Zhu, Lejun
> ---
> v2:
> - Add regmap_config for Crystal Cove.
> v3:
> - Convert IRQ config to
These days, I don't barely look at comedi changes at all because you
guys do such a great job. I just had a process/git comment on this one.
Normally, these changelogs look like:
From: Fred Brooks
Add support for switching the input range and the
single-ended/differential input mode for the AI
On 28 May 2014 15:51, Vivek Goyal wrote:
> On Wed, May 28, 2014 at 10:09:35AM +0800, Dave Young wrote:
>
> [..]
>> > I've only vaguely been following along with the other thread, so please
>> > summarise everything again in your patch. Particularly, I need answers
>> > to the following questions,
On 28 May 2014 20:04, Vivek Goyal wrote:
> On Wed, May 28, 2014 at 10:51:04AM -0500, Alex Thorlton wrote:
>
> [..]
>> A side note, though: We're going to have to figure out some way to
>> determine whether or not to apply the old_map quirk on during boot
>> anyway, so if it's easiest for you to
On Thu, May 29, 2014 at 15:31 +0400, Pavel Emelyanov wrote:
> On 05/29/2014 03:12 PM, Vasily Kulikov wrote:
> > On Thu, May 29, 2014 at 13:07 +0400, Pavel Emelyanov wrote:
> >> On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
> >>> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote:
> >>> ]
> module_i2c_driver simplifies the code by eliminating
> boilerplate code.
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/mfd/menelaus.c | 23 +--
> 1 file changed, 1 insertion(+), 22 deletions(-)
Applied, thanks.
> diff --git a/drivers/mfd/menelaus.c
Hi Amit,
One minor comment.
On Thu, May 29, 2014 at 09:15:30AM +0100, Amit Daniel Kachhap wrote:
> This patch allows the caller of cpufreq cooling APIs to register along
> with their driver data which will be useful while receiving any cooling states
> notifications.
> This patch is in
On Thu, May 29, 2014 at 12:28:45PM +0100, David Howells wrote:
>
> This sequence of commands produces both errors:
>
> mount -t tmpfs lower_layer /lower
> mount -t tmpfs upper_layer /upper
> mkdir /upper/upper
> mkdir /upper/work
> mount -t overlayfs overlayfs /mnt
>
On 2014/05/29 12:51 PM, Dan Carpenter wrote:
> These days, I don't barely look at comedi changes at all because you
> guys do such a great job. I just had a process/git comment on this one.
> Normally, these changelogs look like:
>
> From: Fred Brooks
>
> Add support for switching the input
2014-05-29 18:13 GMT+08:00 Daniel Thompson :
> After 07d410e0) serial: sirf: fix spinlock deadlock issue it is no longer
> possiblet to compile this driver. The rename of one of the spinlocks is
> faulty. After looking at the original patch I believe this is the correct
> fix.
>
> Compile tested
Fix perf probe to find correct variable DIE which has location or
external instance by tracking down the lexical blocks.
Current die_find_variable() expects that the all variable DIEs
which has DW_TAG_variable have a location. However, since recent
dwarf information may have declaration variable
Hi Amit,
On Thu, May 29, 2014 at 09:15:31AM +0100, Amit Daniel Kachhap wrote:
> This patch adds notification infrastructure for any requests related to
> cooling
> states. The notifier structure passed is of both Get/Set type. So the receiver
> of these can sense the new/cur/max cooling state as
2014-05-29 20:18 GMT+08:00 Barry Song :
> From: Stephen Rothwell [s...@canb.auug.org.au]
> Sent: Thursday, May 29, 2014 15:28
> To: Greg KH
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Qipan Li; Barry
> Song
> Subject: linux-next: build failure after merge of the tty tree
>
>
From: Fred Brooks
Add support for switching the input range and the single-ended/
differential input mode for the AI subdevice. We needed to clear the
FIFO of data before the conversion to handle card mode switching
glitches.
[ Minor whitespace fixes and driver comment reformatting. - Ian ]
Hi Arnaldo,
Here is the patch which fixes perf probe to find variable
location correctly, on the recent dwarf format. This is not
related to the SEGV issue which I fixed in previous mail.
Thank you,
(2014/05/29 21:19), Masami Hiramatsu wrote:
> Fix perf probe to find correct variable DIE which
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
> Hi Lorenzo,
>
> On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
> > On platforms implementing CPU power management, the CPUidle subsystem
> > can allow CPUs to enter idle states where local timers logic is lost on
>
Hi Amit,
On Thu, May 29, 2014 at 09:15:34AM +0100, Amit Daniel Kachhap wrote:
> This patch upgrades the ACPI cpufreq cooling portions to use the generic
> cpufreq cooling infrastructure. There should not be any functionality
> related changes as the same behaviour is provided by the generic
>
On Thu, May 29, 2014 at 10:08:37AM +0800, Dave Young wrote:
> On 05/28/14 at 08:40am, Vivek Goyal wrote:
> > On Wed, May 28, 2014 at 10:13:59AM +0800, Dave Young wrote:
> > > On 05/27/14 at 09:34am, Vivek Goyal wrote:
> > > > On Mon, May 26, 2014 at 04:39:35PM +0800, Dave Young wrote:
> > > > >
>
The patch adds backlight support to s6e8aa0 panel.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/panel/Kconfig | 2 ++
drivers/gpu/drm/panel/panel-s6e8aa0.c | 50 +++
2 files changed, 52 insertions(+)
diff --git a/drivers/gpu/drm/panel/Kconfig
On Thu, May 29, 2014 at 08:45:20AM -0400, Vivek Goyal wrote:
> I am curious that what's the meaning of 1:1 mapping here? So far I
> thought that means virt and physical addresses are same but that does
> not seem to be the case. So what does it mean?
1:1 mapping in the EFI's case (and maybe in
On Thu, May 29, 2014 at 2:43 AM, Peter Zijlstra wrote:
>
> See http://marc.info/?l=linux-kernel=139782635207358 and the 20 or so
> patches afterwards.
>
> This has already been done. See a -next tree or so near you.
I think I will start working against the linux-next tree from now on. Thanks!
On 05/29/2014 03:59 PM, Vasily Kulikov wrote:
> On Thu, May 29, 2014 at 15:31 +0400, Pavel Emelyanov wrote:
>> On 05/29/2014 03:12 PM, Vasily Kulikov wrote:
>>> On Thu, May 29, 2014 at 13:07 +0400, Pavel Emelyanov wrote:
On 05/29/2014 09:59 AM, Vasily Kulikov wrote:
> On Wed, May 28, 2014
On Thu, 2014-05-29 at 15:22 +0900, Joonsoo Kim wrote:
> Richard Yao reported a month ago that his system have a trouble
> with vmap_area_lock contention during performance analysis
> by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
> stressfully, but he didn't answer it.
>
>
On Thu, May 29, 2014 at 12:53:19PM +0100, Fleming, Matt wrote:
> On 28 May 2014 15:51, Vivek Goyal wrote:
> > On Wed, May 28, 2014 at 10:09:35AM +0800, Dave Young wrote:
> >
> > [..]
> >> > I've only vaguely been following along with the other thread, so please
> >> > summarise everything again
1101 - 1200 of 1878 matches
Mail list logo
