3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hans Verkuil
commit b339a72e04a62f0b1882c43492fc712f1176b3e6 upstream.
The V4L2_CID_TX_EDID_PRESENT control reports if an EDID is prese
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Douglas Gilbert
commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream.
One of the strange things that the original sg driver did was
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Asai Thambi SP
commit aae4a033868c496adae86fc6f9c3e0c405bbf360 upstream.
Allow device initialization to finish gracefully when it is in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Raghava Aditya Renukunta
commit f88fa79a61726ce9434df9b4aede36961f709f17 upstream.
aac_fib_map_free() calls pci_free_consistent() witho
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Josh Boyer
commit 9c6ba456711687b794dcf285856fc14e2c76074f upstream.
The powermate driver expects at least one valid USB endpoint in it
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit dd504589577d8e8e70f51f997ad487a4cb6c026f upstream.
Some cipher implementations will crash if you try to use them
with
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vladis Dronov
commit 950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d upstream.
The ati_remote2 driver expects at least two interfaces with one
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Yan, Zheng"
commit 1f041a89b4f22cf2e701514f4b8f73a8b1e06a3e upstream.
struct timespec uses 'long' to present second and nanosecond. 'l
This is the start of the review cycle for the Linux 3.19.8-ckt18 stable
kernel.
This version contains 170 new patches, summarized below. The new patches
are posted as replies to this message and also available in this git branch:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y-
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "David S. Miller"
commit fbd40ea0180a2d328c5adc61414dc8bab9335ce2 upstream.
When an inetdev is destroyed, every address assigned to the
On Wed, Mar 23, 2016 at 09:49:26PM -0400, David Bond wrote:
>
> Some ethernet adapter vendors are supplying products which support optional
> (payed license) features. On some adapters this includes a hardware iscsi
> initiator. The same adapters in a normal (no extra licenses) mode of
> operatio
This reverts commit 57d5f9f808b7 ("x86: get_bios_ebda_length()").
get_bios_ebda_length() uses min_t() without including linux/kernel.h.
This may result in build errors with some configurations. Since the
function is not used anywhere in the kernel, let's just drop it.
Cc: Mike Waychison
Signed-o
On 04/01, Neil Armstrong wrote:
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 16f7d33..2efdbab 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -197,6 +197,12 @@ config COMMON_CLK_PXA
> ---help---
> Support for the Marvell PXA SoC.
>
> +config C
This is a note to let you know that I have just added a patch titled
cpu: Provide smpboot_thread_init() on !CONFIG_SMP kernels as well
to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linu
On Fri, 01 Apr 2016, Michal Hocko wrote:
From: Michal Hocko
This is no longer used anywhere and all callers (__down_write) use
0 as a subclass. Ditch __down_write_nested to make the code easier
to follow.
This shouldn't introduce any functional change.
Signed-off-by: Michal Hocko
Acked-by
On Sat, Apr 2, 2016 at 1:36 AM, Doug Smythies wrote:
> On 2016.04.01 12:54 Rafael J. Wysocki wrote:
>>On Fri, Apr 1, 2016 at 8:31 PM, Doug Smythies wrote:
>>> On 2106.034.01 10:45 Srinivas Pandruvada wrote:
On Fri, 2016-04-01 at 16:06 +0200, Jörg Otte wrote:
>>> > > > > >
> Done. Attache
On Thu, Jan 14, 2016 at 5:16 AM, Ulf Hansson wrote:
> On 28 December 2015 at 15:12, Alex Lemberg wrote:
>> Hi Ulf,
>>
>> We succeeded to run FFU via new mmc multi-command ioctl without any code
>> modification,
>> but only by using Single Sector commands (CMD24).
>>
>> From running the FFU and f
ping
On Thu, Mar 24, 2016 at 02:36:56PM +0100, Jiri Olsa wrote:
> On Thu, Mar 24, 2016 at 11:15:06AM +0100, Borislav Petkov wrote:
> > On Thu, Mar 24, 2016 at 10:44:41AM +0100, Jiri Olsa wrote:
> > > hi,
> > > I'm hitting following lines in dmesg:
> > > resource sanity check: requesting [mem 0xf
Hi,
* Peter Ujfalusi [160401 02:34]:
> So what shall we do with the OMAP3 McBSP2/3 sidetone? It has been broken in DT
> boot since the first time we booted OMAP3 with DT... Only in legacy mode we
> can have properly working ST.
Grr.
> I have the second level of patches based on this set (I thin
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-fixes-for-linus
for you to fetch changes up to 2aac7ddf9a410e3
1) Missing device reference in IPSEC input path results in crashes during
device unregistration. From Subash Abhinov Kasiviswanathan.
2) Per-queue ISR register writes not being done properly in macb driver,
from Cyrille Pitchen.
3) Stats accounting bugs in bcmgenet, from Patri Gynther.
4
On 04/01/2016 03:15 PM, Laura Abbott wrote:
On 03/31/2016 07:35 PM, Joonsoo Kim wrote:
On Mon, Mar 28, 2016 at 03:53:01PM -0700, Laura Abbott wrote:
The per-cpu slab is designed to be the primary path for allocation in SLUB
since it assumed allocations will go through the fast path if possible.
On 04/01/2016 02:32 PM, Mathieu Desnoyers wrote:
> - On Mar 31, 2016, at 9:58 AM, Peter Hurley pe...@hurleysoftware.com
> wrote:
>> On 03/31/2016 02:40 AM, Mathieu Desnoyers wrote:
>>> CCing LKML.
>>>
>>> - On Mar 31, 2016, at 5:39 AM, Mathieu Desnoyers
>>> mathieu.desnoy...@efficios.com w
On Sun, Mar 27, 2016 at 03:24:59PM +0800, zhaoxiu.zeng wrote:
> From: Zeng Zhaoxiu
>
> Signed-off-by: Zeng Zhaoxiu
I'm not CC'd on the rest of this series, where you defined parity16().
And I doubt you've tested this. So I'm not applying.
Brian
> drivers/mtd/ssfdc.c | 20 ++--
On 2016.04.01 12:54 Rafael J. Wysocki wrote:
>On Fri, Apr 1, 2016 at 8:31 PM, Doug Smythies wrote:
>> On 2106.034.01 10:45 Srinivas Pandruvada wrote:
>>> On Fri, 2016-04-01 at 16:06 +0200, Jörg Otte wrote:
>> > > > > >
Done. Attached the tracer.
For me it looks like the previous one of t
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.6-rc2
to receive power management and ACPI material for v4.6-rc2 with top-most
commit 8fbd4ade93dc67f035914cd4030f1c58797d9e59
Merge branch 'acpi-processor'
on top of commit f55532a0c0b8
On 04/01/2016 04:20 PM, Dominique van den Broeck wrote:
> Hello Peter,
> Thanks a lot for your review and kind advice !
>
>> I don't see a > 80-col line here?
>
> In fact, it was not even a 80-col issue but a mis-aligned parenthesis
> one. Realign the rows in this state would make them exceed the
It will be easy for him to get me to sign it when I get home from the LF Summit.
I am, more slowly than Martin, working on another pull request for
you, mostly with
some stuff from the linux-next robots. I'll guess I should base my
pull request on rc2 since
that will have Martin's patches in them?
Jon Hunter writes:
> 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 Tegra20/30 devices the PPI type cannot be
> set and so when we attempt to set the type for the ARM TWD inte
The mm-of-the-moment snapshot 2016-04-01-16-24 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
Hello Martin.
Here's an orangefs patch I think should be applied:
https://patchwork.kernel.org/patch/8676461/
You were not cc'd on this as you are not listed as a
maintainer for orangefs.
Should you be?
On Fri, Apr 01, 2016 at 03:57:47PM -0700, Andrew Morton wrote:
> On Thu, 31 Mar 2016 18:38:11 -0800 Kent Overstreet
> wrote:
>
> > Introduce for_each_pagecache_page() and related macros, with the goal of
> > replacing most/all uses of pagevec_lookup().
> >
> > For the most part this shouldn't b
Hello Peter,
Thanks a lot for your review and kind advice !
> I don't see a > 80-col line here?
In fact, it was not even a 80-col issue but a mis-aligned parenthesis
one. Realign the rows in this state would make them exceed the 80th
column.
I tend to agree with the fact that the way it currentl
This patch introduces a function that reverses everything
done by vmbus_allocate_mmio(). Existing code just called
release_mem_region(). Future patches in this series
require a more complex sequence of actions, so this function
is introduced to wrap those actions.
Signed-off-by: Jake Oshins
---
This patch changes vmbus_allocate_mmio() and vmbus_free_mmio() so
that when child paravirtual devices allocate memory-mapped I/O
space, they allocate it privately from a resource tree pointed
at by hyperv_mmio and also by the public resource tree
iomem_resource. This allows the region to be marked
This patch modifies all the callers of vmbus_mmio_allocate()
to call vmbus_mmio_free() instead of release_mem_region().
Signed-off-by: Jake Oshins
---
drivers/pci/host/pci-hyperv.c | 14 +++---
drivers/video/fbdev/hyperv_fb.c | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
Simplify the logic that picks MMIO ranges by pulling out the
logic related to trying to lay frame buffer claim on top of where
the firmware placed the frame buffer.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 80 ++
1 file changed, 35 i
A patch later in this series allocates child nodes
in this resource tree. For that to work, this tree
needs to be sorted in ascending order.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hv/vmbus_drv.c b/drive
In existing code, this tree of resources is created
in single-threaded code and never modified after it is
created, and thus needs no locking. This patch introduces
a semaphore for tree access, as other patches in this
series introduce run-time modifications of this resource
tree which can happen
This series differs from v3 in that it folds in a patch suggested by
the kbuild test robot, substituting resource_size() for directly
calculating the size.
Hyper-V VMs expose paravirtual drivers through a mechanism called
VMBus, which is managed by hv_vmbus.ko. For each parvirtual service
instanc
Later in the boot sequence, we need to figure out which memory
ranges can be given out to various paravirtual drivers. The
hyperv_fb driver should, ideally, be placed right on top of
the frame buffer, without some other device getting plopped on
top of this range in the meantime. Recording this n
From: Rafael J. Wysocki
Add a new cpufreq scaling governor, called "schedutil", that uses
scheduler-provided CPU utilization information as input for making
its decisions.
Doing that is possible after commit 34e2c555f3e1 (cpufreq: Add
mechanism for registering utilization update callbacks) that
On Thu, 31 Mar 2016 18:38:11 -0800 Kent Overstreet
wrote:
> Introduce for_each_pagecache_page() and related macros, with the goal of
> replacing most/all uses of pagevec_lookup().
>
> For the most part this shouldn't be a functional change. The one functional
> difference with the new macros is
omap_rev is used to detect various SoC types, however any misuse of
the usage by invoking it earlier than it being populated will result
in invalid results. Lets flag them as early as possible to prevent
unintended side effects taking place. We get 0 if it is uninitialized
and -1 when detection is
DRA7 has no SAR region for automated save and restore of wakeupgen,
which does not make real since the SoC really does not do legacy OFF
mode anymore. Further wakeupgen should never loose context in CSWR
retention mode for MPU domain on DRA7 since that is the deepest state
we will enter.
So, just
Hi,
series of patches for fixing up attempt to suspend on X15
Test: http://pastebin.ubuntu.com/15582436/
Based on v4.6-rc1
Also needs https://patchwork.kernel.org/patch/8724791/ if kernel
modules are installed
Nishanth Menon (3):
ARM: OMAP: DRA7: wakeupgen: Skip SAR save for wakeupgen
ARM:
When commit 06c2d368fc36 ("ARM: OMAP: DRA7: Make use of omap_revision
information for soc_is* calls") introduced SoC check using
omap_revision, it missed providing DRA7 as class for initializing
the omap_version variable. Without doing this, soc_is_dra7xx() will
fail and as a result, omap4_pm_init_
Hi Linus,
My for-linus-4.6 branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus-4.6
Has a few fixes Dave Sterba had queued up. These are all pretty small,
but since they were tested I decided against waiting for more:
Alex Lyakas (2) commits (+18/-10):
btr
On Fri, Apr 1, 2016 at 2:49 PM, Martin Brandenburg wrote:
> Let's try this again...
Ok, pulled.
That's a brand-spanking new key you have there, can you try to get
that mutually signed with at least Mike, possibly other kernel
developers? Depending on where you are physically, that may be either
On Fri, Apr 01, 2016 at 07:34:10AM +0200, Takashi Iwai wrote:
> On Fri, 01 Apr 2016 00:26:18 +0200,
> Luis R. Rodriguez wrote:
> >
> > On Wed, Mar 30, 2016 at 08:07:04AM +0200, Takashi Iwai wrote:
> > > On Tue, 29 Mar 2016 23:37:32 +0200,
> > > Andy Lutomirski wrote:
> > > >
> > > > Would it be p
On 04/01/2016 12:49 PM, Peter Zijlstra wrote:
> On Sat, Apr 02, 2016 at 12:38:37AM +0800, Leo Yan wrote:
>> When task is migrated from CPU_A to CPU_B, scheduler will decrease
>> the task's load/util from the task's cfs_rq and also add them into
>> migrated cfs_rq. But if kernel enables CONFIG_FAIR_
The following BUG_ON error was reported on QEMU/i386:
kernel BUG at arch/x86/mm/physaddr.c:79!
Call Trace:
phys_mem_access_prot_allowed
mmap_mem
? mmap_region
mmap_region
do_mmap
vm_mmap_pgoff
SyS_mmap_pgoff
do_int80_syscall_32
entry_INT80_32
after commit edfe63ec97ed ("x86/
On Fri, 2016-04-01 at 11:07 +0800, Yangbo Lu wrote:
> This patchset is used to fix a host version register bug in the T4240-R1.0
> -R2.0
> eSDHC controller. To get the SoC version and revision, it's needed to add
> the
> GUTS driver to access the global utilities registers.
>
> So, the first three
Hi Jake,
[auto build test WARNING on v4.6-rc1]
[also build test WARNING on next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Jake-Oshins/drivers-hv-Ensure-that-bridge-windows-don
drivers/hv/vmbus_drv.c:1099:15-18: ERROR: Missing resource_size with fb_mmio
Use resource_size function on resource object
instead of explicit computation.
Generated by: scripts/coccinelle/api/resource_size.cocci
CC: Jake Oshins
Signed-off-by: Fengguang Wu
---
vmbus_drv.c |2 +-
1 fil
On 03/31/2016 07:35 PM, Joonsoo Kim wrote:
On Mon, Mar 28, 2016 at 03:53:01PM -0700, Laura Abbott wrote:
The per-cpu slab is designed to be the primary path for allocation in SLUB
since it assumed allocations will go through the fast path if possible.
When debugging is enabled, the fast path is
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:01 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subje
From: Adrian Hunter
Intel PT uses the time members from the perf_event_mmap_page to convert
between TSC and perf time.
Due to a lack of foresight when Intel PT was implemented, those time
members were recorded in the (implementation dependent) AUXTRACE_INFO
event, the structure of which is gener
From: Arnaldo Carvalho de Melo
This was causing bogus values to be shown at the timestamp column:
Before:
# trace --ev bpf-output/no-inherit,name=evt/ --ev
/home/acme/bpf/test_bpf_trace.c/map:channel.event=evt/ usleep 10
94631143.385 ( 0.001 ms): brk( )
From: Adrian Hunter
For Intel PT / BTS, define the environment variable that selects TSC
timestamps in the jitdump file.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Cc: Stephane Eranian
Link:
http://lkml.kernel.org/r/1457426333-30260-1-git-send-email-adrian.hun...@intel.com
Signed-off-by: Arn
From: Arnaldo Carvalho de Melo
# trace -e getrandom
35622.560 ( 0.023 ms): systemd-udevd/631 getrandom(buf: 0x55621e3c18f0,
count: 16, flags: NONBLOCK) = 16
35622.585 ( 0.006 ms): systemd-udevd/631 getrandom(buf: 0x55621e3c18f0,
count: 16, flags: NONBLOCK) = 16
35622.594 ( 0.004 ms): sy
From: Arnaldo Carvalho de Melo
We catch this record to provide a visual indication that events are
getting lost, then call the default method to allow extra logging shared
with the other tools to take place.
This extra logging was done twice because we were continuing to the
"default" clause whe
From: Arnaldo Carvalho de Melo
That is used in both live runs, i.e.:
# trace ls
As when processing events recorded in a perf.data file:
# trace -i perf.data
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Milian Wolff
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/
From: Wang Nan
Before this patch we can see very large time in the events before the
'bpf-output' event. For example:
# perf trace -vv -T --ev sched:sched_switch \
--ev bpf-output/no-inherit,name=evt/ \
--ev ./test_bpf_trace.c/map:channel.event=evt/
From: Arnaldo Carvalho de Melo
E.g:
# trace -e seccomp
200.061 (0.009 ms): :2441/2441 seccomp(op: FILTER, flags: TSYNC
) = -1 EFAULT Bad address
200.910 (0.121 ms): :2441/2441 seccomp(op: FILTER, flags: TSYNC, uargs:
0x7fff57479fe0) = 0
Cc: Adrian Hunter
Cc: Dav
From: Kan Liang
Currently the max value of format is calculated by the bits number. It
relies on the continuity of the format.
However, uncore event format is not continuous. E.g. uncore qpi event
format can be 0-7,21.
If bit 21 is set, there is parsing issues as below.
$ perf stat -a -e unc
/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20160401
for you to fetch changes up to d37ba880598654fda10b312331377cdca3edd574:
perf bpf: Add sample types for 'bpf-output' event (2016-04-01 18:46:25 -0300)
---
From: Adrian Hunter
Intel PT uses TSC as a timestamp, so add support for using TSC instead
of the monotonic clock. Use of TSC is selected by an environment
variable "JITDUMP_USE_ARCH_TIMESTAMP" and flagged in the jitdump file
with flag JITDUMP_FLAGS_ARCH_TIMESTAMP.
Signed-off-by: Adrian Hunter
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:00 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; sta...
On Fri, Apr 01, 2016 at 02:40:32PM -0700, Steve Muckle wrote:
> On 03/31/2016 02:14 AM, Peter Zijlstra wrote:
> > On Thu, Mar 31, 2016 at 09:59:51AM +0200, Peter Zijlstra wrote:
> >>> > > - passing an argument into attach_entity_load_avg() to indicate
> >>> > >
On Fri, Apr 01, 2016 at 09:34:24PM +0800, Xunlei Pang wrote:
> >> I checked the code, currently only deadline accesses the
> >> pi_waiters/pi_waiters_leftmost
> >> without pi_lock held via rt_mutex_get_top_task(), other cases all have
> >> pi_lock held.
> Any better ideas is welcome.
Something l
On Fri, Mar 11, 2016 at 12:26:57AM +0530, Aniroop Mathur wrote:
> Hi Henrik,
>
> On Thu, Mar 10, 2016 at 7:15 PM, Henrik Rydberg wrote:
> > Hi Dmitry,
> >
> >>> diff --git a/drivers/input/input.c b/drivers/input/input.c
> >>> index 8806059..262ef77 100644
> >>> --- a/drivers/input/input.c
> >>> +
* Tony Lindgren [160401 14:37]:
> We currently try to match of_dev_auxdata based on compatible,
> IO address, and device name. But in some cases we have multiple
> instances of drivers that can use the same auxdata.
>
> Let's add an additional secondary lookup for generic compatible
> match for a
On 03/31/2016 02:14 AM, Peter Zijlstra wrote:
> On Thu, Mar 31, 2016 at 09:59:51AM +0200, Peter Zijlstra wrote:
>>> > > - passing an argument into attach_entity_load_avg() to indicate
>>> > >
>>> > >whether calling the cpufreq hook is necessary
A patch later in this series allocates child nodes
in this resource tree. For that to work, this tree
needs to be sorted in ascending order.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hv/vmbus_drv.c b/drive
This patch modifies all the callers of vmbus_mmio_allocate()
to call vmbus_mmio_free() instead of release_mem_region().
Signed-off-by: Jake Oshins
---
drivers/pci/host/pci-hyperv.c | 14 +++---
drivers/video/fbdev/hyperv_fb.c | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
Later in the boot sequence, we need to figure out which memory
ranges can be given out to various paravirtual drivers. The
hyperv_fb driver should, ideally, be placed right on top of
the frame buffer, without some other device getting plopped on
top of this range in the meantime. Recording this n
We currently try to match of_dev_auxdata based on compatible,
IO address, and device name. But in some cases we have multiple
instances of drivers that can use the same auxdata.
Let's add an additional secondary lookup for generic compatible
match for auxdata if no device specific match is found.
Simplify the logic that picks MMIO ranges by pulling out the
logic related to trying to lay frame buffer claim on top of where
the firmware placed the frame buffer.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 80 ++
1 file changed, 35 i
This patch changes vmbus_allocate_mmio() and vmbus_free_mmio() so
that when child paravirtual devices allocate memory-mapped I/O
space, they allocate it privately from a resource tree pointed
at by hyperv_mmio and also by the public resource tree
iomem_resource. This allows the region to be marked
In existing code, this tree of resources is created
in single-threaded code and never modified after it is
created, and thus needs no locking. This patch introduces
a semaphore for tree access, as other patches in this
series introduce run-time modifications of this resource
tree which can happen
This series differs from v2 in that it reserves not only the memory
in use as the UEFI frame buffer but also the off-screen memory, so
that PCI devices can't reserve that, either.
Hyper-V VMs expose paravirtual drivers through a mechanism called
VMBus, which is managed by hv_vmbus.ko. For each pa
On Fri, 2016-04-01 at 08:46 +0800, Herbert Xu wrote:
> On Thu, Mar 31, 2016 at 05:29:59PM +0200, Johannes Berg wrote:
> >
> >
> > Does removing this completely disable the "-EEXIST" error? I can't
> > say
> > I fully understand the elasticity stuff in
> > __rhashtable_insert_fast().
> What EEXIST
This patch introduces a function that reverses everything
done by vmbus_allocate_mmio(). Existing code just called
release_mem_region(). Future patches in this series
require a more complex sequence of actions, so this function
is introduced to wrap those actions.
Signed-off-by: Jake Oshins
---
Dear RT folks!
I'm pleased to announce the v4.4.6-rt13 patch set.
Changes since v4.4.6-rt12:
- Alexandre Belloni sent patch for the AT91 to get rid of the free_irq()
warning.
- Yang Shi sent a patch to address a "sleeping while atomic" warning in
a writeback tracepoint. Until now it was disa
- On Mar 31, 2016, at 9:58 AM, Peter Hurley pe...@hurleysoftware.com wrote:
> Hi Mathieu,
>
> On 03/31/2016 02:40 AM, Mathieu Desnoyers wrote:
>> CCing LKML.
>>
>> - On Mar 31, 2016, at 5:39 AM, Mathieu Desnoyers
>> mathieu.desnoy...@efficios.com wrote:
>>
>>> Hi,
>>>
>>> Code review (r
Might have been better as a separate migration patch and then a compaction
patch. It's prefixed mm/compaction, but most changed are in mm/migrate.c
On 03/30/2016 09:12 AM, Minchan Kim wrote:
We have allowed migration for only LRU pages until now and it was
enough to make high-order pages. But r
Am Samstag, 02 April 2016, 03:51:21 schrieb kbuild test robot:
> >> arch/powerpc/include/asm/ftrace.h:62:5: error: "CONFIG_PPC64" is not
> >> defined [-Werror=undef]
> #if CONFIG_PPC64 && (!defined(_CALL_ELF) || _CALL_ELF != 2)
> ^
>cc1: all warnings being treated as errors
I forgo
Version 2 of the Server Base System Architecture (SBSAv2) describes UART
hardware registers as 32 bits wide, giving no guidance on access sizes. The
SBSA UART driver previously assumed partial-length 16 and 8 bit accesses would
work. But the SBSAv2 UART hardware on the Qualcomm Technologies QDF2432
Hi!
> >>It would have the same downsides as in case of having r, g and b in
> >>separate attributes, i.e. - problems with setting LED colour in
> >>a consistent way. This way LED blinking in whatever colour couldn't
> >>be supported reliably. It was one of your primary rationale standing
> >>behin
Hi Mark,
thanks for the continued feedback - please see below.
On Wed, Mar 30, 2016 at 08:38:53AM -0700, Mark Brown wrote:
> On Tue, Mar 29, 2016 at 09:53:18PM -0500, Andreas Dannenberg wrote:
> > On Mon, Mar 28, 2016 at 08:01:43PM +0100, Mark Brown wrote:
> > > On Mon, Mar 21, 2016 at 12:08:27PM
* Mike Galbraith | 2016-03-31 08:31:43 [+0200]:
>3. nuke irksome grab_lock: make everybody always try to get the hell
>outta Dodge or hotplug can bloody well wait.
>
>I haven't yet flogged my 64 core box doing that, but my local boxen
>seem to be saying we don't really really need the grab_lock bu
From: Stuart Yoder
-The Freescale Management Complex and all associated objects
use message interrupts, and thus an msi-parent is required.
-Define a ranges property to specify the mapping between
the MC address space and the system address space.
-The fsl-mc node may optionally have dpmac su
From: Stuart Yoder
This patch series adds a few missing things from the binding
for the fsl-mc node on the ls2080a Soc-- msi-parent, ranges,
dpmac definition. The ls2080a device tree is updated to
reflect the binding updates.
Stuart Yoder (2):
Documentation: fsl-mc: binding updates for MSIs,
From: Stuart Yoder
updates to the fsl-mc node for full functionality:
-msi-parent is needed for interrupt support
-ranges is needed to enable the bus driver to translate bus addresses
-dpmac nodes provide a basis for relating dpmac objects to PHYs
Signed-off-by: Stuart Yoder
---
arch/
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:00 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; sta...
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 1:19 PM
> To: Vitaly Kuznetsov
> Cc: KY Srinivasan ; o...@aepfle.de;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; a...@canonical.com;
> de...@linuxdriverproject.org
> Subject
On Friday, April 01, 2016 01:52:54 PM Viresh Kumar wrote:
> On 30-03-16, 13:18, Rafael J. Wysocki wrote:
> > It conflicts with other stuff (as you know), so I'm not sure about the
> > order in which they are going to be applied, though.
>
> Please let me know when can I rebase and resend this one.
On Fri, Apr 01, 2016 at 02:26:35PM +0200, Boris Brezillon wrote:
> Standardize the NAND controller/NAND chip DT representation. Now, all new
> NAND controller drivers should comply with this representation, even if
> they are only supporting a single NAND chip.
>
> Existing drivers can keep suppor
If cldrv->probe() failed in mei_cl_device_probe(),
the mei module is left pinned.
The patch moves __module_get(THIS_MODULE) after cldrv->probe().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/misc/mei/bus.c | 8 ++--
1 file cha
201 - 300 of 890 matches
Mail list logo
